proactivenet release notes

BMC ProactiveNetVersion: 8.6.02July 26, 2011

BMC Software is releasing version 8.6.02 of BMC ProactiveNet. These release notes provide information about the enhancements and resolved problems in this version. This information supplements and supersedes information in the documents listed in “Solution documents” on page 73.

Overview of BMC ProactiveNet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3What’s new in BMC ProactiveNet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

New supported platforms and third-party product versions. . . . . . . . . . . . . . . . . . 3BMC Cloud Lifecycle Management environment . . . . . . . . . . . . . . . . . . . . . . . . . . . 4BMC ProactiveNet Data Collection Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4New screen to integrate BMC ProactiveNet with BMC BladeLogic . . . . . . . . . . . . 5New BMC ProactiveNet Performance Management Support and Compatibility

Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5New CLI commands to create, edit, and delete SLOs . . . . . . . . . . . . . . . . . . . . . . . . 5

Installation considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5When installing on 64-bit Windows, do not install into the Program Files (x86)

directory path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Checking the UDDI registry login and the WSDL link . . . . . . . . . . . . . . . . . . . . . . . 6BMC Performance Manager Portal integration patch requirement. . . . . . . . . . . . . 7Required patch for BMC PATROL for WebLogic with BMC ProactiveNet

Application Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Installation and upgrade considerations for BMC Impact Event Adapters . . . . . . 7Installation consideration for the SNMP Adapter Configuration Manager . . . . . . 8Installation and upgrade considerations for Integration for BMC Remedy Service

Desk (IBRSD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9BMC ProactiveNet Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

What’s new in BMC ProactiveNet Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Open issues and workarounds in BMC ProactiveNet Server. . . . . . . . . . . . . . . . . 11Closed issues and workarounds in BMC ProactiveNet Server . . . . . . . . . . . . . . . 14

NOTE Before you install the solution, check the Customer Support website at http://www.bmc.com/support_home for updated information about this version. Flashes, technical bulletins, and resolutions on the site contain details about any fixes that were issued for this version after its release.

Release Notes

*211133**211133*

*211133*

http://www.bmc.com/support_home

2 Release Notes July 26, 2011

BMC ProactiveNet Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Open issues and workarounds in BMC ProactiveNet Agent . . . . . . . . . . . . . . . . . 15Closed issues and workarounds in BMC ProactiveNet Agent . . . . . . . . . . . . . . . . 17

BMC ProactiveNet Operations Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17What’s new in the BMC ProactiveNet Operations Console . . . . . . . . . . . . . . . . . . 17What’s changed for the BMC ProactiveNet Operations Console . . . . . . . . . . . . . . 19Open issues and workarounds in the BMC ProactiveNet Operations Console . . 20Corrected issues in BMC ProactiveNet Operations Console. . . . . . . . . . . . . . . . . . 22Open issues and workarounds in the BMC ProactiveNet Performance

Management Package Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24BMC ProactiveNet Administration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

What’s new in the BMC ProactiveNet Administration Console. . . . . . . . . . . . . . . 25What’s changed in the BMC ProactiveNet Administration Console . . . . . . . . . . . 26Open issues and workarounds in BMC ProactiveNet Administration Console . 27Corrected issues in BMC ProactiveNet Administration Console . . . . . . . . . . . . . . 31

BMC Impact Event Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32What’s new in BMC Impact Event Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Open issues and workarounds in BMC Impact Event Adapters . . . . . . . . . . . . . . 32Corrected issues in BMC Impact Event Adapters. . . . . . . . . . . . . . . . . . . . . . . . . . . 35

BMC ProactiveNet Monitors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35What’s changed in BMC ProactiveNet Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Open issues in BMC ProactiveNet Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Corrected issues for BMC ProactiveNet Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . 38

BMC Impact Integration Web Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39What’s new in BMC Impact Integration Web Services . . . . . . . . . . . . . . . . . . . . . . 39What’s changed in BMC Impact Integration Web Services . . . . . . . . . . . . . . . . . . . 40Open issues and workarounds in BMC Impact Integration Web Services . . . . . . 41Closed issues in BMC Impact Integration Web Services . . . . . . . . . . . . . . . . . . . . . 42

BMC ProactiveNet CMDB Extensions and BMC Impact Model Designer . . . . . . . . . 42Open issues in BMC ProactiveNet and BMC Atrium CMDB integration . . . . . . . 43Corrected issues in BMC ProactiveNet and BMC Atrium CMDB integration . . . 44

Integration for BMC Remedy Service Desk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44What’s new in Integration for BMC Remedy Service Desk. . . . . . . . . . . . . . . . . . . 44Open issues and workarounds in IBRSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Corrected issues in IBRSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

BMC ProactiveNet Publishing Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Open issues and workarounds in the BMC ProactiveNet Publishing Server. . . . 50Corrected issues in BMC ProactiveNet Publishing Server . . . . . . . . . . . . . . . . . . . 54

Upgrades from BMC Impact Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55What’s new in upgrades from BMC Impact Solutions. . . . . . . . . . . . . . . . . . . . . . . 55Special KB migration instructions for hybrid upgrade: BMC Event and Impact

Management 7.xx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Open issues with upgrades from BMC Impact Solutions to BMC ProactiveNet . 66

Upgrading in virtualization environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66BMC ProactiveNet Performance Management Triage and Remediation solution. . . 67

Open issues and workarounds in the Triage and Remediation solution . . . . . . . 67Documentation corrections and clarifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

BMC ProactiveNet documentation errata. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Updates to the pw group add_subgroup section in the BMC ProactiveNet

Command Line Reference Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Overview of BMC ProactiveNet

BMC ProactiveNet version 8.6.02 3

Downloading from the web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Support for BMC ProactiveNet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Solution documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Full-text search of solution documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Where to view the latest solution information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74How to obtain the solution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Customer support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Overview of BMC ProactiveNetBMC ProactiveNet combines powerful data collection with robust enterprise-scalable event collection and management, allowing monitoring and event management on a single, integrated platform. BMC ProactiveNet ensures complete coverage of your IT infrastructure by supplementing data and event collection with third-party events and data when native data collection is unavailable or not feasible. With predictive capabilities, intelligent event and impact management, coverage for virtualized environments, and a role-based console, BMC ProactiveNet helps IT prioritize IT issues and perform quicker root cause analysis, thus automating and closing the gap between problem detection and resolution processes.

What’s new in BMC ProactiveNetThe following section lists some of the new features in BMC ProactiveNet version 8.6.02. For information about new features for a specific component, see the section pertaining to that component.

New supported platforms and third-party product versions

Support for Oracle

BMC ProactiveNet version 8.6.02 is supported on the Oracle database. BMC ProactiveNet supports standalone Oracle version 11.2.0.2.0.

NOTE This document refers to a licensed product delivered in the BMC ProactiveNet platform. The BMC ProactiveNet platform name appears prominently in the user interfaces. BMC ProactiveNet is licensed under the BMC ProactiveNet Performance Management solution. Depending on what license add-on you purchased, some functionality might be unavailable from the BMC ProactiveNet user interfaces.

BMC Cloud Lifecycle Management environment


For more information about using BMC ProactiveNet with Oracle, see the BMC ProactiveNet Getting Started Guide.

Support for BMC Atrium CMDB 7.6.04 SP1 and BMC Atrium CMDB 7.6.03 P1

BMC ProactiveNet version 8.6.02 can be integrated with BMC Atrium CMDB 7.6.04 SP1 and BMC Atrium CMDB 7.6.03 P1. For information about BMC ProactiveNet and BMC Atrium CMDB supported versions, see the BMC ProactiveNet Performance Management Support and Compatibility Matrix.

BMC Cloud Lifecycle Management environment

BMC ProactiveNet Performance Management supports the BMC Cloud Lifecycle Management environment. In the BMC Cloud Lifecycle Management environment, you can use BMC ProactiveNet Performance Management to monitor the performance of devices, including virtual machine monitors (VMMs, also called hypervisors), clusters, and host servers. For more information, see the BMC Cloud Lifecycle Management 2.0.00 online technical documentation.

BMC ProactiveNet Data Collection Host

BMC ProactiveNet Data Collection Host is a new component of BMC ProactiveNet Performance Management. It is a dedicated computer used to collect metric data from devices, including virtual machines, clusters, and host servers. The data collection host sends the data to the BMC ProactiveNet Server for analysis. Collected data includes CPU usage, memory usage, and data specific to the host operating system. For more information, see the BMC ProactiveNet Deployment Guide.

BMC ProactiveNet Data Collection Host is also used in the BMC Cloud Lifecycle Management environment. Each BMC ProactiveNet Server in the BMC Cloud Lifecycle Management environment requires one ProactiveNet Data Collection Host. For more information about the data collection host in the cloud environment, see the BMC Cloud Lifecycle Management 2.0.00 online technical documentation.

NOTE To change the username/password that BMC ProactiveNet uses to connect to the Oracle database, contact Customer Support.

New screen to integrate BMC ProactiveNet with BMC BladeLogic


New screen to integrate BMC ProactiveNet with BMC BladeLogic

The BMC BladeLogic Connection Information screen is a new screen in the BMC ProactiveNet installer. This screen lets you integrate BMC ProactiveNet with BMC BladeLogic. For more information about integrating with BMC BladeLogic, see the BMC ProactiveNet Getting Started Guide.

New BMC ProactiveNet Performance Management Support and Compatibility Matrix

The BMC ProactiveNet Performance Management Support and Compatibility Matrix is a new document that contains information about supported operating systems, hardware, software, database, and applications requirements for the components of BMC ProactiveNet Performance Management. The BMC ProactiveNet Performance Management Compatibility Matrix is available on the BMC Support website.

New CLI commands to create, edit, and delete SLOs

You can now create, edit, and delete a Service Level Objective (SLO) by executing commands from the BMC ProactiveNet Server's Command Line Interface (CLI) prompt. The following commands have been introduced:

■ pw slo add

■ pw slo edit

■ pw slo delete

For information about the syntax of these commands, arguments that can be used, examples and limitations, see the BMC ProactiveNet Command Line Reference Guide.

Installation considerationsBefore installing the product, review the following sections. These sections supplement the information in the BMC ProactiveNet Getting Started Guide.

When installing on 64-bit Windows, do not install into the Program Files (x86) directory path


When installing on 64-bit Windows, do not install into the Program Files (x86) directory path

Do not install into a directory path that includes \Program Files (x86). Due to a known issue with Apache, if you install into a directory path that contains \Program Files (x86), the product will not function.

Checking the UDDI registry login and the WSDL link

If you plan to integrate BMC ProactiveNet with BMC Atrium CMDB, you must check the UDDI registry login and the WSDL link to verify that the Web services are running properly.

The port numbers in the URL below is located at <atriumcore_home>/AtriumCoreInstalledConfiguration.xml

To verify the UDDI registry login (for BMC Atrium CMDB versions 7.6.03 patch 1 and BMC Atrium CMDB versions 7.6.04 SP1)

■ Use the http://<web_services_host>:<bmc_reg_jsp_tomcat_http_port>/uddi URL (for BMC Atrium CMDB versions 7.6.03 patch 1 and 7.6.04 SP1). Log in with the default user name and password of admin/admin.

For example, http://vm-p2423-rds1342:7777/uddi

To verify the WSDL link

■ For BMC Atrium CMDB version 7.6.03 patch 1https://<web_services_host>:<bmc_wsi_https_port>/atriumws7603/services/atrium_notifications_pull/atrium_notifications_pull.wsdl

For example, https://vm-p2423-rds1342:8443/atriumws7603/services/atrium_classes/atrium_classes.wsdl

■ For BMC Atrium CMDB version 7.6.04 SP1https://<web_services_host>:<bmc_wsi_https_port>/atriumws7604/services/atrium_notifications_pull/atrium_notifications_pull.wsdl

For example, https://aus-ngp-vm156:3801/atriumws7604/services/atrium_classicreconciliation.wsdl

BMC Performance Manager Portal integration patch requirement


BMC Performance Manager Portal integration patch requirement

If you plan to integrate with BMC Performance Manager Portal version 2.7.50, you must install the BMC Performance Manager Portal patch version 2.7.00.050. BMC ProactiveNet requires this version of the patch to successfully integrate with BMC Performance Manager Portal. For more information about the patch, see the patch technical bulletin on the BMC Software Customer Support site: http://documents.bmc.com/supportu/documents/61/92/106192/Output/09186a3380622fad.htm

Required patch for BMC PATROL for WebLogic with BMC ProactiveNet Application Diagnostics

If you want to collect information from WebLogic systems using BMC ProactiveNet Application Diagnostics (that is, BMC ProactiveNet integration with BMC AppSight), you must install the BMC PATROL for WebLogic KM version 2.10.00 with patch srp1678476f1 and add the following pconfig variable:

/BEAWLS_SERVER/IncludeMachineName = true

After updating the pconfig variable, restart the BMC PATROL Agent.

If you do not install the patch and add the pconfig variable, BMC ProactiveNet Application Diagnostics will not be able to collect data from WebLogic.

Installation and upgrade considerations for BMC Impact Event Adapters

Required prior to upgrade and uninstall: manually clean up Perl and msend processes

Stopping the Perl based-adapters service does not kill the Perl process. Because the Perl service is still running, one of its msend processes continues to run. Killing the Perl process does not kill the msend process. This prevents the upgrade utility and the uninstall utility from cleaning up and causes multiple Perl processes to be running if the service is restarted.

http://documents.bmc.com/supportu/documents/61/92/106192/Output/09186a3380622fad.htm

Installation consideration for the SNMP Adapter Configuration Manager


To prevent this issue from occurring, follow these steps before upgrading or uninstalling BMC Impact Event Adapters:

1 Manually stop the BMC Impact Event Adapters service.

2 Ensure that all Perl and msend processes are stopped. If necessary, kill msend and Perl processes using the Windows Task Manager.

3 Upgrade or uninstall the component.

Pre-installation Perl version requirement

Before installing BMC Impact Event Adapters, ensure that the appropriate version of Perl is installed as described in the BMC ProactiveNet Performance Management Support and Compatibility Matrix.

Installation consideration for the SNMP Adapter Configuration Manager

The SNMP Adapter Configuration Manager will not install or run properly if the Install Net-SNMP Library feature is used on Microsoft Windows Server 2003, SP1 or Microsoft Windows Server 2003 X64 (32-bit compatibility mode).

1 Before you install the SNMP Adapter Configuration Manager, install the Net-SNMP Library included on the BMC Event and Impact Management Base installation DVD. The net-snmp files are located in the net-snmp directory.

2 Install the SNMP Adapter Configuration Manager, pointing to the existing sub-directories (such as c:\usr\mibs and c:\usr\bin) using the paths available when you select Don't Install Net-SNMP Library.

To start the SNMP Adapter Configuration Manager on Solaris and Linux systems:

1 Set the LD_LIBRARY_PATH environment variable to $MCELL_HOME/bin.

2 Navigate to the $MCELL_HOME/bin directory.

3 Execute ldd libESNMPReceiver.so.

A list of .so files that are not found is displayed.

4 Add the paths of these files to the LD_LIBRARY_PATH environment variable.

Installation and upgrade considerations for Integration for BMC Remedy Service Desk (IBRSD)


Installation and upgrade considerations for Integration for BMC Remedy Service Desk (IBRSD)

Preferred drive format

NTFS is the preferred drive format for IBRSD installations. Installation on WIN FAT 32 drives can cause unpredictable results.

Installation of IBRSD modules

The IM module and integration module of IBRSD are installed automatically when you install BMC ProactiveNet Performance Management version 8.5 or later. The AR System module of IBRSD is installed in a separate installation program.

For details about installing BMC ProactiveNet, see the BMC ProactiveNet Getting Started Guide. For details about installing the AR System module of IBRSD, see the Integration for BMC Remedy Service Desk User Guide.

Installing IBRSD on non-English locales

The IBRSD installation utility checks for a particular log with English text. If that text is returned in any other language, then the install fails.

The AR System module must be installed under the EN locale. After the installation has completed, you can change to a non-EN locale.

Upgrading to IBRSD 7.4.00 from Impact Solutions version 7.2.x or 7.3.x

IBRSD 7.4.00 is now installed as a part of the BMC Impact Solutions installation. Earlier versions of IBRSD had three modules that you needed to install.

■ IBRSD - BMC IM module■ IBRSD - Integration module■ IBRSD - AR System module

If you have these three modules installed, to upgrade the IBRSD - BMC IM and IBRSD integration modules, use the BMC Impact Solutions 7.4.00 installation program. To upgrade the IBRSD - AR System module, run the IBRSD - AR installation program separately.

BMC ProactiveNet Server


Upgrading from BMC Impact Integration for Remedy AR System to IBRSD

If you are using BMC Impact Integration for Remedy AR System, you must uninstall it before installing IBRSD. Before you uninstall it, back up the data.

BMC ProactiveNet ServerThis section describes the enhancements and changes specific to BMC ProactiveNet Server for this release, and issues that remain open and that have been corrected.

What’s new in BMC ProactiveNet Server

The following sections describe the new features in BMC ProactiveNet Server.

Parameters for metrics collection

You can specify two new parameters for metrics collection in the mcell.conf file:

■ CellMetricsCollectInterval

The CellMetricsCollectInterval parameter determines the interval length (in seconds) of a single collection. Metrics from a single collection are presented in short term metrics counters. You can also specify the default value.

For example, CellMetricsCollectInterval=60

■ CellMetricsCollectAmount

The CellMetricsCollectAmount parameter specifies the number of single collections that must be taken into account. The combination of the most recent collections is presented in medium term metrics counters.

NOTE ■ When upgrading, for both IBRSD IM and IBRSD Integration modules, the BMC Impact

Solutions installer uninstalls them and reinstalls the new integration module as part of the solution installation.

■ The earlier IBRSD - BMC IM module is now a part of the cell Knowledge Base.■ You only need to upgrade the IBRSD - AR System module separately.

For detailed information, see the “Installing IBRSD” chapter from the Integration for BMC Remedy Service Desk User Guide.

Open issues and workarounds in BMC ProactiveNet Server


For example, CellMetricsCollectAmount=5


The following issues remain open in this release of BMC ProactiveNet. If a tracking ID has been assigned, it is provided.

Tracking ID Issue

QM001711954 mccomp fails and displays the following error message after migrating the Knowledge Base (KB):

BMC-IMC120100E: No slot notification_service defined for class CORE_EVENT

This is because the definition of the slot selector_ecf has changed from EVENT to CORE_EVENT in the im_policies.baroc file.

Workaround:

1. Open the im_policies.baroc file.

2. Locate and change selector_ecf : ECF CORE_EVENT; to selector_ecf : ECF EVENT;

3. Recompile the KB with mccomp.

QM001711476 If you are using BMC ProactiveNet with the Oracle database, you cannot upgrade BMC ProactiveNet version 8.6.01 (a version of the product which was released to a limited number of customers) to version 8.6.02.

QM001711455 If you are performing a silent uninstallation of BMC ProactiveNet on a Microsoft Windows system, the system reboots automatically without warning after the uninstallation.

BMC recommends not to perform any operation during the course of the silent uninstallation.



QM001704758 When you deploy the BMC ProactiveNet Server using the Cloud Lifecycle Management planner in a Proof of Concept (POC) deployment, the planner does not set the recommended heap size for BMC ProactiveNet processes. This may lead to data collection issues after running successfully for a few days.

Recommendation: You need to manually set the recommended heap size for BMC ProactiveNet processes on the system running the BMC ProactiveNet Server. To manually set the recommended heap size:

1. Stop the BMC ProactiveNet Server using the pw system stop command.

2. Change the heap size parameter in the following files located at <bmc_proactivenet_server_home>\pw\pronto\conf:

■ pnagent.conf: MaxHeap=1024 MB■ pnjserver.conf: MaxHeap=2048 MB■ pnrate.conf: MaxHeap=2048 MB

3. Start the BMC ProactiveNet Server using the pw system start command.

QM001703016 Sometimes, the Sybase ASA version 11.0.1 database may hang.

In this case, check if more than 24 logical processors are on the system in which the BMC ProactiveNet Server is running. If the number of logical processors is more than 24, use the following workaround.

Workaround: Edit the pw\pronto\conf\pndbsrv.conf file and add following statement:

COMDefine -gtc 24

Save the changes and restart the BMC ProactiveNet Server.

QM001697574 The database goes down for 1 minute during the auto synchronization period for adapters. All devices and monitors are imported to the BMC ProactiveNet Server during the next auto synchronization period.

QM001696152 Executing the pw license update command may display the following error:

Connection to rate lost. Dropped Message 8 java.net.SocketException: Connection reset by peer: socket write error

You can ignore this error. If this error occurs frequently during the course of a BMC ProactiveNet Server operation, contact BMC support.

QM001696034 Sometimes, the system in which the BMC ProactiveNet Server is installed may receive a false e-mail message that the BMC ProactiveNet cell is not running even though all the processes are running. This is an intermittent issue that may occur when during the installation of the BMC ProactiveNet Server.

QM001695621 In the BMC Cloud Lifecycle Management environment, if the BMC PATROL Agent stops for more than two hours, device instances that were added through the BMC PATROL adapter are deleted (instead of being retained). Instance history is lost after this time.

Tracking ID Issue



QM001695112 If the connection between the BMC ProactiveNet Server and the remote agent breaks during the auto-sync process, the failed application classes do not get imported.

Workaround: Edit the adapter, select the application classes that were not imported and import them manually.

QM001697768 If you are using BMC ProactiveNet on Oracle, and the size of the datafile exceeds 2-3 MB, the following error message is written to the proactivenet.log file:

ORA-01653: unable to extend table PROACT.AUTODISCOVERY_ERRORS by 8 in tablespace NGP_TS

Workaround: Contact the Oracle administrator to create a new datafile.

QM001680983 Running the pw license update command to apply a new license on Solaris systems may take a long time to initialize. You may also require a long time log on to the Administration Console.

Workaround: Restart the BMC ProactiveNet Server using the pw system start command instead of pw license update.

QM001680564 In the BMC Cloud Lifecycle Management environment, when a landing BMC ProactiveNet Server is uninstalled, the router BMC ProactiveNet Server retains the landing server's cache.

Workaround: Restart the router BMC ProactiveNet Server after uninstalling the landing server to clear the cache.

QM001680443 On BMC ProactiveNet version 7.7 patch 4, if you created an adapter on the same system as the remote agent and PATROL Agent, after upgrading to 8.5, all monitors appear under a single device under the remote agent. If you edit the existing adapter, another device is created under the server.

QM001677398 If the Integration Service is enabled on the BMC ProactiveNet Server version 8.5, the pw sys stop command does not stop the Integration Service process. This in turn, does not allow you to upgrade to version 8.6.02 and prompts that some of the files are locked.

Workaround: Run services.msc and change the start-up type of the BMC ProactiveNet Server, database, and the Integration Service to Manual. Restart the system and try to upgrade again.

QM001647699 UTF-8 encoded locales must be installed on the system in which the BMC ProactiveNet Server and Agents are installed.

QM001635822 A central ProactiveNet Server does not receive events from an originating ProactiveNet Server following a change to either server’s host name in CMDB.

Workaround: Create a new device alias for the ProactiveNet Server whose host name was changed in CMDB.

Tracking ID Issue

Closed issues and workarounds in BMC ProactiveNet Server


Closed issues and workarounds in BMC ProactiveNet Server

The following issues were closed this release of BMC ProactiveNet.

QM001624987 (Windows only): You will encounter rollover stop for ProactiveNet.log during the following three scenarios:

■ Running the tail command against ProactiveNet.log ■ Opening the ProactiveNet.log file using Notepad++, edit++, or textpad from a remote

machine particularly when the log size is 10MB■ If a logfile monitor is created against ProactiveNet.log and data collection timing

matches the rollover time.

Workaround: Close or suspend the tail process or Notepad++ process, if you encounter the first two issues. Disable the log file monitor for the third issue.

QM001623026 When the BMC ProactiveNet Server is set up in failover mode using Windows Cluster, if you are connected to node 1 of the cluster and failover occurs, then the BMC ProactiveNet Operations Console cannot be used to perform operations.

Workaround: Re-log into the BMC ProactiveNet Operations Console and then perform operations.

QM001615209 A Null Pointer Exception inappropriately is written to the proactivenet.log file when the BMC ProactiveNet Server is shut down.

Issues in non-English version

QM001675580 On non-English operating systems, installing BMC ProactiveNet on Solaris 10 may not work.

Workaround: Set the LANG environment variable to C for the installation to work. After the installation, you can set the variable back to your local locale. However, you must manually set the pronet.system.language property in pronet.conf file for the local locale. The pronet.conf file is located at <bppm_server_install_path>/pw/pronto/conf.

For example, for Korean, modify the pronet.conf file as shown below:

pronet.system.language property=ko

Tracking ID Issue

QM001704555 The end action does not run at the end of the scheduled timeframe.

QM001704423 Local timeframes might work incorrectly when daylight saving time is applied.

QM001690841 Updating the data_reception slot does not update the date slot.

QM001688717 Only a maximum number of eight dynamic enrichment policies execute.

Tracking ID Issue

BMC ProactiveNet Agent


BMC ProactiveNet AgentThis section describes the enhancements and changes specific to the BMC ProactiveNet Agent for this release and issues that remain open.

Open issues and workarounds in BMC ProactiveNet Agent


QM001679922 While upgrading the BMC ProactiveNet Server to version 8.5, if the Tunnel Agents (SSL) belong to an earlier version, the agents may not be connected to the Server.

Workaround:

1. Copy the following line to the httpd.conf and httpd-ssl.conf files. Both these files are located at <bmc_proactivenet_server_home>/apache/conf.

SSLInsecureRenegotiation on

2. Copy pnagent.ks and pnagenthttps.ks from <bmc_proactivenet_server_home>/pw/pronto/conf to <bmc_proactivenet_agent_home>/Agent/pronto/conf

QM001649408 The msetmsg command applies only to external events to change the status of events. The command is not applicable to Intelligent Events.

QM001632493 Upon upgrade on a standby node in a Windows cluster setup, events are missing in the cell but are present in EG_EVENT.

QM001640692 Uninstallation on Solaris Server does not remove the event-related files from the /etc/rc3.d directory.

Tracking ID Issue

QM001712687 Installing the remote agent overwrites the pronet.conf and pnagent.conf files. If you have customized these files, take a backup before installing the remote agent. Once the remote agent is installed, restore these files from the backup.

QM001711857 Installing the remote agent overwrites the cell KB. If you have customized the KB, take a backup of the KB before installing the remote agent. Once the remote agent is installed, restore the cell KB from the backup.

QM001705283 Encryption of passwords in the <file_name>.options file is not supported during an unattended installation of the BMC ProactiveNet Agent. However, the BMC ProactiveNet Getting Started Guide incorrectly states that encryption of passwords is supported.

Encryption of passwords is supported during an unattended installation of the BMC ProactiveNet Server.

Tracking ID Issue

Open issues and workarounds in BMC ProactiveNet Agent


QM001617099 If you want to install multiple BMC ProactiveNet Agents on a system, you must install them as root. If you do not, multiple cells will be installed, all named as the host name. This can cause problems when the cells attempt to interact with the cell on the central ProactiveNet Server.

QM001649935 BMC ProactiveNet displays multiple devices for the same host as the BMC PATROL adapter creates adapters according to FQDN even if you have not specified it.

QM001677630 Edit and add operations on timeframes of policies do not work on remote cells older than 7.4.00 in the BMC ProactiveNet environment.

Workaround: Upgrade remote cells to BMC ProactiveNet version 8.5.00 Agent cells.

QM001678218 The Tunnel Agent does not connect to the BMC ProactiveNet Server while upgrading from BMC ProactiveNet version 2.5 to version 3.

QM001696326 If you install a BMC ProactiveNet Agent of an earlier version after installing the BMC ProactiveNet Agent version 8.6.02 on the same system, the BMC ProactiveNet Agent version 8.6.02 may not work as expected. Do not install an earlier version of the BMC ProactiveNet Agent on the same computer in which a BMC ProactiveNet Agent version 8.6.02 is already installed.

QM001697032 On Microsoft Windows systems, the uninstallation of a BMC ProactiveNet Agent that was installed for the first time in high availability mode does not remove the folders in the following path: BMC_PROACTIVENET_AGENT_HOME\UninstallBPPMAgent.

The uninstallation of an upgraded BMC ProactiveNet Agent does not remove the top-level Agent installation directory, but it does remove the underlying files and subdirectories.

QM001698495 On Solaris and Linux systems in which more than one BMC ProactiveNet Agent is installed, when you start the Integration Service, the staging adapter starts on the default port (port 3183).

For the staging adapter to run on a specified port, perform the following steps:

1. In the Administration Console, go to Tools > Configure > Integration Service.

2. Select a source Agent, enter the host name of the Integration Service, and enter the port number on which the staging adapter must run.

3. Click Next.

4. Click Configure Integration Service.

5. Change the value of the port attribute for the _SA_DEFAULT_ profile.

6. Start the BMC PATROL Agent to bind the port you specified.

Tracking ID Issue

Closed issues and workarounds in BMC ProactiveNet Agent


Closed issues and workarounds in BMC ProactiveNet Agent

The following issues have been closed in this release of BMC ProactiveNet.

BMC ProactiveNet Operations ConsoleThis section describes what’s new in the BMC ProactiveNet Operations Console and also the issues that remain open and the issues that have been corrected.

What’s new in the BMC ProactiveNet Operations Console

The following sections describe the new features for the BMC ProactiveNet Operations Console.

Tracking ID Issue

QM001615882 The TCP Monitor can cause errors in the ProactiveNetAgent.log file.

QM001635502 The BMC ProactiveNet installation utility allows the BMC ProactiveNet Agent to be installed on an unsupported platform.

QM001675709 Multiple devices are created and displayed after you upgrade a BMC ProactiveNet 8.1 Agent to a BMC ProactiveNet 8.5 Agent. To avoid duplicate device creation, follow these steps:

1. Open the configuration file BMC_PROACTIVENET_AGENT_HOME\Agent\monitors\shared\MF3PatrolAdapter\MF3PatrolAdapter.conf.

2. Remove the following entry from the file:

removePortNumInDeviceName = “true”

3. Save and close the file.

4. Restart the BMC ProactiveNet Agent.

QM001680909 When installing the remote agent on port 1828, the BMC ProactiveNet installer fails to detect if the port is busy or occupied by another process.

What’s new in the BMC ProactiveNet Operations Console


Creating and installing PATROL Knowledge Module packages

When you install the BMC ProactiveNet Server, you have the option to install the BMC ProactiveNet Performance Management Package Installation Repository. The Package Installation Repository includes all the BMC PATROL Knowledge Modules (KMs) that can be integrated with BMC ProactiveNet, as well as the BMC PATROL Agent.

From the Operations Console, administrators can select the KMs they want to install from the repository on the same host(s) and package these KMs together so that they can be installed simultaneously.

After creating a PATROL KM package, administrators can:

■ save the package to the Package Installation list for future use

■ install the package on the current host without saving the package

■ download and install the package on any host

For information about how to create and install BMC PATROL KM packages, see the BMC ProactiveNet User Guide.

Sending manual events

This feature allows you to demonstrate erroneous events, if any, with minimal time and effort to the support team. For information about using this feature, see the BMC ProactiveNet User Guide.

Saving a quick filter setting

Quick filters show events based on a specific status, severity level, time, event type, device, or groups. In BMC ProactiveNet Performance Management version 8.6, you can save the quick filter settings for event collectors and event collections, and go back to the last saved filter settings. For more information about quick filters and saving quick filters, see the BMC ProactiveNet User Guide.

Viewing the total number of filtered events

You can now view the total number of events for which filters have been applied. This number is displayed next to the Event(s) label on the Details pane. For more information, see the BMC ProactiveNet User Guide.

What’s changed for the BMC ProactiveNet Operations Console


Viewing the total number of configuration items

You can acquire a total count of configuration items (CIs) from the Find CI accordion in the BMC ProactiveNet Operations Console. The total number of CIs that match your search results is displayed against the Results label in the Find CI accordion.

Filtering objects in the Graph view by severity

By default, no filter is applied to the Graph view. You now can use the filter menu to filter the Graph view based on severity of the objects that make up that service and meet the filter criteria. Objects that do not meet the selected filter criteria are grayed out, but are still viewable to maintain the context of the view. For more information, see the BMC ProactiveNet User Guide.

HTML link in the Tile View Preferences dialog box

In the Tile View Preferences dialog box, you can now enter a hyperlink as the custom text you want to display in a tile. Supported hyperlink formats are http://, https://, ftp://, and www. For more information, see the BMC ProactiveNet Performance Management User Guide.

What’s changed for the BMC ProactiveNet Operations Console

BMC ProactiveNet Operations Console includes the following feature changes.

Generating baselines for KPI attributes

When the Enable Abnormality Detection and Baseline Generation for non-KPI metrics check box is not selected, baselines are generated for KPI attributes. When the check box is selected, baselines are generated for both KPI and non-KPI attributes that have abnormal thresholds.

Open issues and workarounds in the BMC ProactiveNet Operations Console




Tracking ID Issue

QM001709513 Cross-launching the BMC ProactiveNet Operations Console from an instance of the BMC ProactiveNet Operations Console belonging to another BMC ProactiveNet Server may not work if the server response time is slow.

QM001705574 Events of abnormality type are not displayed in the CI events list when the scope of events is set to Direct.

Workaround: Set the scope of events to All (Direct and Providers) to view CIs of abnormality type.

QM001704976 When you click the Find CI accordion, sometimes, the search results may not display any CIs.

Workaround: Wait for 4 to 5 minutes and click Find CI again. The search results will be displayed.

QM001704430 In the BMC ProactiveNet Operations Console, when a partition is added to a view, the view is dropped and recreated. During this process, JServer is unable to access the database view, and displays the Table or view does not exist error message.

QM001701235 If you are using Oracle and the database connection is down, you are not logged out of the Operations Console when BMC ProactiveNet is trying to reconnect to Oracle. As a result of this, the database and the BMC ProactiveNet cell may not be synchronized.

QM001701233 If the Oracle database is disconnected from BMC ProactiveNet, you must restart the BMC ProactiveNet Server.

QM001691837 If you are accessing the Operations Console in Mozilla Firefox, and try to navigate from one folder to another in the Main accordion, you may not be able to select events.

Workaround: Refresh the browser.

QM001680589 In the Operations Console tile view, for the BMC_StorageSubsystem class, the class name is not displayed in the configuration item (CI) tile.

QM001680213 In the Operations Console, the option to disable the Predictions pane is no longer available in Notebook Details preferences for all devices.

QM001677970 In the SLO Console, if you create an SLO compliance matrix report with an ampersand (&) special character in the instance name and you select SLO Compliance Matrix report, click on the SLO name that includes the ampersand (&), click Graph, then click Show Parent, a Java NullPointerException error message is displayed.

Workaround: Click the Custom Graph Generator link from the same page and generate a fresh graph.

QM001675983 If you try to access BladeLogic Device History for a device that has been deleted, an Illegal Argument Exception occurs.



QM001674707 When you upgrade from BMC ProactiveNet 8.1 to BMC ProactiveNet 8.5, the Details notebook tabs are not displayed for the Graph View.

Workaround: Select a configuration item (CI) object in the Graph View, open the Details notebook preferences dialog box, select the tabs that you want to display, and close the dialog box to save your selections. For a description of the Details notebook and instructions for setting notebook preferences, see the BMC ProactiveNet User Guide.

QM001674407 Remote action results are not displayed for the Modify Slot Value remote action.

QM001666190 Duplicate CIs are created on a BMC ProactiveNet cell if the cell has published a CI with host and domain and a BMC adapter discovers the same CI without a domain.

Workaround: If you create and publish a CI and then try to discover the same CI using a BMC adapter, ensure that you provide the host name and domain of the CI in its respective provider product. If you don't provide these details, a duplicate CI is created.

QM001665727 Out-of-the-box abnormality thresholds cannot be deleted using the pw threshold delete command.

QM001664568 For any note added to an event from a remote cell of version 7.3.xx or earlier, the Source column in the Logs & Notes dialog box (accessed from the Logs & Notes tab on the event notebook) displays PPM instead of displaying the user name of the user that added the note.

QM001664420 Abnormality thresholds viewed from the BMC ProactiveNet Operations Console are different from the abnormality thresholds generated using the pw threshold command.

QM001664005 If you add a cell earlier than version 7.3 as a remote cell and log in to the BMC ProactiveNet Operations Console as a user of the Event Administrators group, you will not be able to perform any of the event operations (such as Assign, Acknowledge, Close, and so on). Also, no event collectors are displayed in the Operations Console for this cell.

To view the collector hierarchy for the remote cell, specify the Event Administrators role in the .mrl file of the required collector. The .mrl file is located at <install_directory>\Impact\server\etc\<cell_name>\kb\collectors.

Recompile the cell KB and restart the cell.

QM001655316 When generating a graph, if you select the Show Graph for the last 1 hour option, the end time of the graph is one hour ahead of the current time. This issue only occurs for time zones that do not consider Daylight Savings Time (DST).

Workaround: Change your time zone to one that considers DST (for example, (GMT-6:00) Central Time (US & Canada)). Use the Date and Time setting on the Control Panel to change the time zone, and deselect the Automatically adjust clock for daylight saving changes check box. Now, change the time zone to the one that you require, and restart the BMC ProactiveNet Server.

QM001638801 When used with BMC ProactiveNet, SNMP Configuration Manager 7.3.00 throws a java.lang.NullPointerException exception. This occurs because of an incorrect variable value set for MCELL_HOME.

Workaround: Edit the catalina.bat file (installed with SNMP Configuration Manager) to correct the variable value for MCELL_HOME to show the correct path. Restart SNMP Configuration Manager.

Tracking ID Issue

Corrected issues in BMC ProactiveNet Operations Console



The following problems were reported in earlier releases of the BMC ProactiveNet Operations Console and have been corrected in this release.

QM001637444 When you export an event, the exported CSV file is encoded in Unicode Transformation Format (UTF-8). You cannot view multi-byte characters in this CSV file encoded in UTF-8 in Microsoft Excel.

Workaround: Use another text editor, such as, Notepad on Windows to view the UTF-8 encoded CSV file.

QM001625764 You cannot open the BMC ProactiveNet Operations Console from the tray icon on several Windows 2003 operating system locales.

Workaround: Open the BMC ProactiveNet Operations Console from the Window Start menu.

QM001624469 While you are executing the Remote actions/Diagnostics using psExec protocol, the following commands fail to show output in Test button window of BMC ProactiveNet Administrator console and Operations console, even when the exit code returns to zero.

■ tasklist /fi "memusage gt 40000"■ cmd c/ "net view "■ netsh diag show all■ net view


QM001680059 If you are using BMC ProactiveNet in Korean, when you launch BMC Atrium Explorer from the BMC ProactiveNet Operations Console, some of the BMC Impact Model Designer menu options may appear in English.

QM001673160 If non-English characters are included in event description of the Windows Event View on non-English operating systems, the entire description is not visible in the More Info for Graph table in the Operations Console.

QM001620802 When running on Korean Windows 2003 SP2, and a remote action is executed against an event, broken characters might appear in the Action Details.

Tracking ID Description

QM001682690 The PDF utility for a thumbnail on a view shows no data in the graph.

Workaround: Click Generate Graph(s) in the view before clicking the PDF icon.

QM001676240 ■ If you delete a BMC BladeLogic device, BMC BladeLogic history for that device is no longer available.

■ The default throttling logic time has changed from 10 minutes to 20 minutes.

QM001671711 For remote cells of version 7.1, the Related events pop-up list will not display the action performed event (the event that is generated when you perform a remote action on an event).

Tracking ID Issue



QM001665453 When you use the slider bar to resize the tile to the smallest possible size, tile drill-down is not possible.

QM001639431 Composite threshold values are not computed appropriately when the threshold is set with the Weekly Baseline being enabled.

QM001636776 If you select a device in the navigation tree that has monitors associated with it and create a Canvas view for that device, when you switch to Grid view, drill down on that device to view the monitors, and then switch back to the Canvas view, the device tile is no longer displayed.

QM001636312 If you launch the Operations Console in Microsoft Internet Explorer 6 or Microsoft Internet Explorer 7, the Operations Console stops responding if the Event list or Grid view is left idle for a long period of time.

QM001636286 When you add the Score column to the default event list using the Quick Columns Selector, the assigned width (65) hinders the display of the Score icon.

QM001634591 Operation history is not logged or added when you close an Intelligent Event from the Operations console.

QM001633879 If you use the Tab Preferences option in the Options window to remove the Events Console tab from the Operations Console, the Operations Console is not configured correctly and navigation issues could result.

QM001633641 If the Operations Console is idle for more than one hour, the following error message is displayed:

The connection to the ProactiveNet server had been lost. This may be due to a network problem or the server may be unavailable.

QM001626932 The version of the abnormality score icon that appears in the operations console is different from the version that appears in the administration console.

QM001624595 Event Details in the Notebook pane can fail to display.

QM001623897 When cell data is reloaded, you must login again to the Operations Console.

QM001619373 The Dial Gauge graph does not take baselines into consideration while displaying the threshold value.

QM001619006 While executing Remote actions/Diagnostics using psExec protocol, the command output is incomplete.

QM001576787 If you select a single attribute as the Monitor Attribute Selector, the baseline reset functionality does not work.

QM001637676 When you create a device in the Administration Console and you use a special character in the device name, then you can not see the monitors for the device when you click on the device name in the Grid view of the BMC ProactiveNet Operations Console.


QM001647699 UTF-8 encoded locales must be installed on the system in which the BMC ProactiveNet Performance Management Server and Agents are installed.


Open issues and workarounds in the BMC ProactiveNet Performance Management Package Installer


Open issues and workarounds in the BMC ProactiveNet Performance Management Package Installer


Tracking ID Issue

QM001703169 If you are adding a new component to the Package Installation Repository on Solaris systems using Internet Explorer 7, an error message is displayed.

QM001701713 Installation packages for UNIX and Linux operating systems fail to deploy on IBM AIX 6.1 systems in the WPAR environment.

Workaround: If the installation fails on IBM AIX 6.1 systems in the WPAR environment, go to <patrol_home_directory> and run the following utilities provided by BMC PATROL:

■ set_default_account.sh

■ set_default_port.sh

QM001701697 Installation packages for UNIX and Linux operating systems display error messages after being deployed on a SUSE Linux Enterprise Server x64 system.

QM001701692 Installation packages for UNIX and Linux operating systems fail to deploy on AIX VIOS systems.

Workaround: Copy install/instbin/install.sh in to the extracted bmc_products directory and execute install.sh.

QM001700119 While creating a BMC PATROL installation package, if you enter multi-byte characters in the Name field, the name is displayed as junk characters in the Component Installation Packages table.

QM001699993 If you create an image for a UNIX system, save it as a .zip file, and extract it on a UNIX system, installation may fail. You must create images for UNIX systems in .tar or tar.gz formats or if created in .zip format, must run the chmod -R 755 bmc_products command after extracting the .zip file.

QM001699811 The RunSilentInstall utility does not display an error message if it fails to execute. See the installation log files located in the parent installation directory (C:\Program Files\BMC Software\log) for the status of the installation.

QM001699419 While installing some KMs without an agent, a Can't preload error message is displayed. This does not affect the installation.

QM001699369 If you create a Sybase KM installation package using the BMC ProactiveNet Operations Console, you are prompted to provide root credentials. This does not affect the installation in any manner.

QM001698042 While creating an installation package, sometimes, a KM specific to an operating system is pre-loaded although it is not included in the package. This does not have an effect on the installation.

BMC ProactiveNet Administration Console


BMC ProactiveNet Administration ConsoleThis section describes the enhancements and changes specific to the BMC ProactiveNet Administration Console for this release, and issues that remain open and that have been corrected.

What’s new in the BMC ProactiveNet Administration Console

The following sections describe the new features in the Administration Console.

Configuring cell connection properties to the BMC ProactiveNet Server

In BMC ProactiveNet Performance Management version 8.6, you can use the Server Impact Manager Settings and the Server Impact Manager Properties dialog boxes to configure the connection between the BMC ProactiveNet Server and the BMC ProactiveNet cells that you create.

Viewing child classes under the CORE_EVENT class

When you add an event selector, all the child classes belonging to the CORE_EVENT class are displayed in the Class Chooser dialog box.

Verifying BMC PATROL instance-to-device mapping in BMC ProactiveNet

This feature converts all instances that contain FQDN and TokenId to devices and displays appropriate icons in the BMC ProactiveNet Operations Console.

Instances that are not converted to devices due to the unavailability of FQDN and TokenId, will be available under the parent device.

QM001691452 While creating a BMC PATROL installation package, if you enter multi-byte characters in the Description field, the description is not saved and does not appear in the Component Installation Packages table.

QM001689835 If you use the Back button on the package installation utility screens, an error message may be displayed in the installation UI.

Tracking ID Issue

What’s changed in the BMC ProactiveNet Administration Console


In BMC ProactiveNet version 8.5, the BMC PATROL Agent provider component was at the root of the VM hierarchy but in version 8.6.02, the virtual center (VC) is at the root of the VM hierarchy. The BMC PATROL Agent provider component is displayed as an individual device.

Converting CSV data to enrichment data

You can use the mcsvtodde command to convert CSV data to data compatible in the Dynamic Enrichment Match table. For information about using mcsvtodde, see the BMC ProactiveNet Command Line Interface Reference Guide.

New parameters for mcontrol metrics

The following new parameters have been added to the mcontrol metrics command:

■ interval

This parameter allows you to change the length of the collection interval for medium term metrics.

■ amount

This parameter allows you to change the amount of collection intervals for medium term metrics.

For example, mcontrol metrics interval 60 amount 5

What’s changed in the BMC ProactiveNet Administration Console

BMC ProactiveNet Administration Console includes the following feature enhancements.

Change in behavior while adding an adapter for BMC PATROL

While adding an adapter for BMC PATROL using the automated workflow, if an adapter or the remote agent associated to the adapter is deleted, devices, instances and groups with respect to that adapter are also deleted. In earlier versions, only instances with respect to that adapter were deleted.

Open issues and workarounds in BMC ProactiveNet Administration Console




Tracking ID Issue

QM001713560 For a failover job to work, an adapter must be created.

QM001710263 The PATROL Configuration Manager fails to launch from the BMC ProactiveNet Administration Console.

Workaround: Set the pcm.home environment variable so that it points to the PATROL Configuration Manager installation directory. That is, set pcm.home to C:\Program Files\BMC Software\pconfmgr.

QM001705572 If a VC is removed from the BMC PATROL agent, even though devices are deleted from BMC ProactiveNet, they may still appear on the BMC ProactiveNet Operations Console and BMC ProactiveNet Administration Console.

Workaround: Restart JServer to resolve this issue.

QM001704355 While upgrading BMC ProactiveNet from version 8.5 to version 8.6.02, configuration data is fetched only from the newly installed instance of the PATROL Configuration Manager (installed automatically when the Administration Console is installed). Data from the PATROL Configuration Manager installed during the earlier version is not fetched.

Workaround: Take a backup of the .ini and rulesets directory (located at C:\Program Files\BMC Software\ProactiveNet Admin\admin\pcm\pconfmgr) from an older installation of PATROL Configuration Manager before the upgrade and copy the files to the new installation location of BMC ProactiveNet version 8.6.02.

QM001702433 If the virtual machine (VM) discovered is part of the Microsoft Windows workgroup (DNS name ends with a “.” in the VI client for such VMs), and the VM was already added to BMC ProactiveNet as a device using some other channel (for example, as a BMC ProactiveNet Agent, or a BMC PATROL Agent), it results in a duplicate device.

QM001698783 When you edit an adapter instance and deselect a few application classes, the respective devices do not get deleted.

QM001698452 If a remote agent is associated with an adapter instance, when you delete the remote agent, the adapter instance and its devices are also deleted. Only the remote agent device is not deleted.



QM001696534 Adding the BMC PATROL agent monitoring VM using the VSM KM and the local BMC PATROL agent does not consolidate the monitors.

Workaround:

■ If the agents are running on different ports, import the agent monitoring the node locally and agent(s) monitoring the node remotely (using UNIX, Microsoft Windows, VMware, Xen, Hyper-V remote monitoring solution) from the same Integration Service.

■ If the agents are running on the same port, import the agent monitoring the node locally and agent(s) monitoring the node remotely (using UNIX, Microsoft Windows, VMware, Xen, Hyper-V remote monitoring solution) from two different instances of the Integration Service.

QM001694910 The BMC PATROL agent is not added to a profile when incorrect credentials (wrong user name or password) are subsequently corrected.

Workaround: Remove the BMC PATROL agent and add it with the correct credentials.

QM001687834 When a VC (virtual center) is deleted from the BMC PATROL agent, some of the monitor instances are not marked to be deleted and the associated devices not de-provisioned during the following auto-sync.

Workaround: Monitor instances and devices that are not marked to be deleted get marked for delete after 24 hours if the auto-sync interval is 15 minutes, or after 96 auto-sync polls. Edit the adapter instance for the instance to be marked for delete immediately.

QM001686921 On Microsoft Windows 2008, saving a recorded script using the Web Capture Tool displays an error message.

Workaround: Copy the TranFile.dtd file from \pw\pronto\usr_apps\webtranx to pw\admin.

QM001676271 When a component alias uses a backslash (\) character, then the alias in the BMC ProactiveNet Administration Console appears with four backslashes (\\\\).

QM001675500 If you create and execute a remote action for event management and specify the credentials of the remote system in the credential_repository.xml file, in the Service Impact Graph page, the following error message is displayed:

Credentials not found in Repository

Workaround: Provide the IP address instead of the host name as credentials in the credential_repository.xml file.

QM001638754 New HP OVO agents are not discovered automatically when the Automatically add new agents (auto-sync) check box is selected in the Import Agents from HP OVO Server dialog box.

Workaround: Connect to the HP OVO Proxy, configure the HP OVO Proxy environment with the required agents, and then add the agents to an existing HP OVO Proxy environment or create a new environment.

Tracking ID Issue



QM001637842 You can not add a device to more than one BMC ProactiveNet Server using the same Administration Console session.

Workaround: After adding the device to one BMC ProactiveNet Server from the Administration Console, exit the current session, launch a new session that connects to a different BMC ProactiveNet Server, and add the device to that server.

QM001632226 The Administration Console does not display the UDB Catalog cache size value correctly if the DB2 instance has AUTOMATIC configuration on MAXAPPLS which is referred in CATALOGCACHE_SZ.

QM001630374 When you edit or delete an adapter instance in an Administration Console that is connected to a BMC ProactiveNet Server installed on a Solaris computer, the process might time out.

Workaround: Before you edit or delete the adapter, increase only the Auto-sync Poll Timeout period in the Schedule Auto-sync Polls of the Edit dialog box for the adapter, and then click Finish. Then you can perform the required action. For more information, see the BMC ProactiveNet Administrator Guide.

QM001626473 Remote action policies will not work if the tagged/associated detail diagnostics is renamed or deleted.

Workaround: You can edit the policy and attach other detail diagnostics but cannot change the name of Remote action policy.

QM001624472 When you execute four Remote Actions/Detail Diagnostics simultaneously for an alarm using psExec protocol, the following message is displayed with the error code 121.

All pipe instances are busy

Workaround: Execute one remote actions / detail diagnostics for one alarm to avoid All pipe instances are busy

QM001619272 The DateList in the TimeFrame window is not displayed in English.

Workaround: Modify the calendar.date.list.pattern and calendar.date.pattern properties in the pw/admin/lib/lang/en/TimeFrame_timeframe_en_US.properties file.

QM001677630 You cannot add or edit timeframe policies on remote cells older than the current version of the remote cell (either BMC ProactiveNet version 8.5.00 or BMC Impact Solutions version 7.4.00).

Workaround: Upgrade the cells in your environment to the current version.

Tracking ID Issue



QM001674657 When a device is created from the Portal Adapter, then the uniqueId from the Portal is also stored for that device. If that device is deleted and recreated again in the Portal, then its uniqueId will be different. When this occurs, the Portal Adapter is not able to create the device because a CMDB-synced device still exists with a different Portal uniqueId.

Workaround:

1. Set the PublishToSIM flag of the computer system CI to No in the CMDB and publish the CI to BMC ProactiveNet.

2. If the corresponding device does not have monitor instances, it will be deleted. Otherwise, delete the device manually.

3. Edit the Portal adapter to include the device.


QM001635533 On Solaris computers, the default time zone is incorrect in the Edit Configuration dialog box in the BMC ProactiveNet Administration Console for Korean locales.

Workaround: Manually change the time zone in the Edit Configuration dialog box.

QM001632360 When you create a log file from Detailed Diagnostics, the output does not work when used with log files encoded in non-native format.

Workaround: Use the Log File Search monitor and specify the correct encoding while creating the monitor.

QM001632668 In the BMC ProactiveNet Administration Console for Korean and Japanese locales, when adding a remote action targeting the Solaris operating system, the output can display broken multi-byte characters.

QM001624552 On computers configured for Korean or Japanese locales, if a user name that contains multi-byte characters and an odd number of syllables is used to log on to the BMC ProactiveNet Administration Console, the log on fails.

Workarounds:

■ When creating new users in BMC ProactiveNet, ensure that the user names that you define have an even number of syllables.

■ For user accounts created outside of BMC ProactiveNet, such as with LDAP, change the user names with an odd number of syllables to user names with an even number of syllables.

Tracking ID Issue

Corrected issues in BMC ProactiveNet Administration Console


Corrected issues in BMC ProactiveNet Administration Console

The following problems were reported in earlier releases of the BMC ProactiveNet Administration Console and have been corrected in this release.


QM001674205 If you have two devices, one created by adding a PATROL adapter, and the other obtained from CMDB, you can view both these devices in the BMC ProactiveNet cell as well as in the JServer server.

If you change the name of one of these devices to the name of the other so that both the devices have the same name and then publish, you can view both these devices in the JServer server but only one device will be displayed in the BMC ProactiveNet cell.

QM001648755 If http port 80 is disabled and http is started at a custom http port and the ProactiveNet server is accessed across a firewall, the Group/Service tree is not accessible.

QM001647719 After creating a service and clicking on the navigation tree to display the service, attempts to display legends by clicking the Show Legends button can result in a partial display of the legends.

QM001646130 When performing an upgrade from BMC ProactiveNet 8.0 to BMC ProactiveNet 8.1, spaces at the beginning or end of attributes specified in a user-defined monitor are not truncated; therefore, the monitors will not work properly after the upgrade is complete.

QM001644768 When attempting to create a system monitor while non-root Solaris Remote Agents are connected to a Windows or Solaris Server, permission-denied errors occur and prevent system monitor creation. The errors are written to the BMC ProactiveNet Agent log.

QM001637874 If you create a template for a ping or traceroute monitor and define remote monitor instances within the template, when you apply the template to another device, the IP address for the remote agents of the monitor instances is changed to the IP address for the device on which you are applying the template.

QM001637676 When you create a device in the Administration Console and you use a special character in the device name, then you can not see the monitors for the device when you click on the device name in the Grid view of the BMC ProactiveNet Operations Console.

QM001619846 An event does not get associated to a device if the event alias contains the fully qualified domain name of the device and the device name does not.

QM001615045 Due to a Java limitation, the wrong time zone is displayed when added scheduled down time for a device.

QM001673676 On Windows, when you upgrade from BMC ProactiveNet 8.0 or 8.1 to BMC ProactiveNet 8.5, you can have two different versions of the remote administration console on the same system. The Control Panel’s Add/Remove Programs feature only lists version 8.5 of BMC ProactiveNet. To uninstall the earlier version, go to driveLetter:\BMC_PROACTIVENET_HOME\ProactiveNet Admin\UninstallBMCProactiveNet and click uninstall.exe.

QM001678849 The direct feed configuration items that are created by mposter and pposter are not receiving the generated alias in the TokenId format (ComponentAlias) of the BMC_ComputerSystem class.

Deprecated Web Services


Deprecated Web ServicesBMC ProactiveNet Performance Management Web Services has been deprecated as of BMC ProactiveNet version 8.6.02.

BMC Impact Event AdaptersThis section provides information about the changes for this release.

What’s new in BMC Impact Event Adapters

This section describes new features in BMC Impact Event Adapters.

Support for BMC Impact Event Log Adapter for Windows

BMC Impact Event Log Adapter for Windows is now supported on Microsoft Windows 2008 R2 platforms.

Open issues and workarounds in BMC Impact Event Adapters


QM001669063 When both the cell and the Impact Administration Server reside on the same Windows system and the PsExec authentication protocol is used for remote action, you may see incomplete results output when you recompile the cell’s KB, restart the IAS, and execute the action or PxExec may fail with an error message.

QM001680157 If you add a PATROL Agent to the Integration Service after creating the adapter instance, it may take a few auto synchronization polls for the hierarchy to be displayed properly.




Table 1 Open issues and workarounds in BMC Impact Event Adapters (part 1 of 3)

Tracking number Issue

QM000504784QM001538010

I18N—When using the BMC Impact Event Log Adapter for Windows, a backslash (\) character is incorrectly displayed in a Japanese MBCS event message in BMC IX.

Workaround: Make the following changes to the $MCELL_HOME/lib/perl/MC/BInstance.pm file:

Comment the $val =~ s/(["\\])/$1$1/g; line as follows:

#$val =~ s/(["\\])/$1$1/g;

And add the following lines:

my $ustr = Encode::decode("shift_jis",$val);$ustr =~ s/(["\\])/$1$1/g;$val = Encode::encode("shift_jis",$ustr);

QM000519786 The SNMP Adapter Configuration Manager will not install or run properly if the Install Net-SNMP Library feature is used on Microsoft Windows Server 2003, SP1 or Microsoft Windows Server 2003 X64 (32-bit compatibility mode). The SNMP Configuration Manager works only with Internet Explorer and does not work with Mozilla.

Workaround: Before you install the SNMP Adapter Configuration Manager, install the Net-SNMP Library (see Note below). When you install SNMP Adapter Configuration Manager, point to the existing sub-directories (such as c:\usr\mibs and c:\usr\bin) using the paths available when you select Don't Install Net-SNMP Library.

Note:

■ The net-snmp files are included on the BMC Impact Manager Enabling Components CD or on the BMC Impact Solutions DVD, in the net-snmp directory. This directory includes the files for net-snmp 5.0.1 and ucd-snmp 4.2.3. However, BMC Software recommends that they be obtained from http://www.net-snmp.org/download.html.

■ Do not start Apache Tomcat from $CATALINA_HOME\bin\startup.bat.

QM001579507 Starting an adapter with the ./mcxa.sh T::6 command results in the following error: "Error at line 13, column 2: Unexpected end of input".

QM001556418 (I18N) On Japanese locales, each Logfile message is displayed twice under the Logfile collector in Impact Explorer.

QM001613587 Events from MCXA(SNMP) become visible 10 minutes after the failover to the secondary cell server.

QM001644813 The evalupper subroutine in Map.pm does not return from the subroutine if the variable passed as the argument is empty or undefined. If the subroutine does not return when the variable is undefined, the following error is returned:

Use of uninitialized value in transliteration (tr///) at /usr/local/bmc/Impact/server/lib/perl/MA/Map.pm line 1409.

QM001666190 If you create and publish a configuration item (CI) and then try to discover the CI using a BMC adapter, ensure that you provide the hostname and domain of the CI in its respective provider product. If you do not provide these details, a duplicate CI is created.

http://www.net-snmp.org/download.html



QM001671573 The SNMP v3 adapter is not supported on the BMC ProactiveNet Server adapter configuration because by default, the BMC ProactiveNet Server deploys Perl version 5.8 and this is not supported for SNMP v3. SNMP v3 requires Perl version 5.12. However, the SNMP v3 adapter is supported on the BMC ProactiveNet Agent. You can install the required Perl version on the BMC ProactiveNet Agent.

QM001679076 The SNMP adapter version 3 will not start on Windows if the zlib1.dll file is not present.

Workaround: Use the following procedure to add the zlib1.dll file:

1. From the command prompt, execute the command mcxa.cmd.

2. A message that zlib1.dll is not present is displayed.

3. Download the zlib.dll from http://www.dlldump.com/download-dll-files_new.php/dllfiles/Z/zlib1.dll/1.2.1.1429r/download.html.

4. Copy the downloaded zlib1.dll to C:\Windows\System32 directory.

5. Click Start and select Run.

6. Type CMD and press Enter.

7. Type cd C:\Windows\System32 and press Enter.

8. Type regsvr32 zlib1.dll and press Enter.

QM001698361 On Solaris and Linux operating systems, the SNMP Adapter Configuration Manager cannot be installed on the system in which BMC ProactiveNet is installed.

Workaround: Copy the setup_env.sh file from $MCELL_HOME/bin to etc/mcell.



http://www.dlldump.com/download-dll-files_new.php/dllfiles/Z/zlib1.dll/1.2.1.1429r/download.html

Corrected issues in BMC Impact Event Adapters


Corrected issues in BMC Impact Event Adapters

The following problems were reported in earlier releases of BMC Impact Event Adapters and have been corrected in this release.

BMC ProactiveNet MonitorsThis section provides what’s new, what’s changed, corrected issues, and the issues that remain open for the BMC ProactiveNet Monitors.

QM001699028 On Solaris and Linux operating systems, the SNMP adapter version 3 does not start if the LD_LIBRARY_PATH variable is not updated.

Workaround:

Set the LD_LIBRARY_PATH environment variable to $MCELL_HOME/bin, where $MCELL_HOME is the location of the BMC ProactiveNet cell’s home directory. For example, /opt/bmc/Impact/server.

QM001700155 On Solaris and Linux operating systems, while running Apache Tomcat, accessing the http://<host_name>:8080/snmpadapter URL may display an error message.

Workaround:

1. Stop the Apache Tomcat server (go to $CATALINA_HOME/bin and run shutdown.sh)

2. Go to $CATALINA_HOME/bin and open catalina.sh.

3. Comment the . /etc/mcell/setup_env.sh line.

4. Add the path in which the setup.env file resides.

5. Start the Apache Tomcat server by running the startup.sh file.


QM001675678 The RUNNING.txt file (installed when you install the SNMP Adapter Configuration Manager) recommends that the Tomcat server be started using the startup.bat file.

Fix: Start the Tomcat server using the run.bat file located at <install_directory>/SNMPAdapter

For example, if you have installed BMC ProactiveNet in the default directory, run.bat is located at C:\Program Files\BMC Software\SNMPAdapter.



What’s changed in BMC ProactiveNet Monitors



This section describes what has changed for BMC ProactiveNet Monitors.

Deprecated monitors

The following BMC ProactiveNet monitors are on limited support as of version 8.6.02. These deprecated monitors will not be supported in the next major release of BMC ProactiveNet Performance Management. Use BMC PATROL Knowledge Module for new monitoring needs. For information on PATROL Knowledge Modules, see the documentation for the specific PATROL Knowledge Module that you are using.

For information on previously supported monitors, see the BMC ProactiveNet Monitor Guide for version 8.5.0 of BMC ProactiveNet.

For information on currently supported monitors, see the BMC ProactiveNet Data Adapter and Monitor Guide.

■ Application monitors

■ IP Services monitors

■ Mail monitors

■ Network monitors

Java Virtual Machine (JVM) monitors WebLogic Server monitor

JBoss monitors WebLogic 5.1 Server monitor

WebLogic JMX monitor WebSphere monitors

Domain Name Service (DNS) monitors Sun ONE Directory Server monitors

Port monitors

Internet Message Access Protocol (IMAP) monitors

POP3 monitors

Exchange SMTP Queue monitors Round Trip E-mail monitors

Microsoft Exchange Round Trip E-mail monitors

SMTP monitors

Microsoft Exchange monitors

Interface MIB monitors TCP monitors

Ping monitors Trace Route monitors

SNMP Agent Availability monitors Windows Mapped Drive monitors



■ System Monitors

■ Database monitors

■ Web monitors

■ Aggregate monitors

Adapter for VMware Solaris Process monitors

Agent Connection monitors Solaris System monitors

Agent Status monitors Solaris TCP monitors

Configuration Command Output Change monitors

Windows CPU monitors

Configuration File Change monitors Windows Disk Performance monitors

File Size monitors Windows Event monitors

Host MIB monitors Windows File System monitors

Linux CPU monitor Windows Process monitors

Linux Disk Performance monitors Windows Service monitors

Linux File System monitors Windows System monitors

Linux Process monitors Windows TCP monitors

Linux System monitors X86 Solaris CPU monitors

Linux TCP monitors X86 Solaris Disk Performance monitors

Log File monitors X86 Solaris File System monitors

Solaris CPU monitors X86 Solaris Process monitors

Solaris Disk Performance monitors X86 Solaris System monitors

Solaris File System monitor X86 Solaris TCP monitors

MS SQL Server Query monitors Oracle Rollback Segment monitors

MS SQL Server Intelliscope 6.5 monitors Oracle Session Wait Event monitors

MS SQL Server Intelliscope monitors Oracle System Wait monitors

Oracle Intelliscope monitors Oracle Table-Space monitors

Oracle Latch monitors Sybase ASA Intelliscope monitors

Oracle Query monitors Sybase Query monitors

Oracle RAC Intelliscope monitors

Apache Web Server monitors Tomcat Connector monitors

IIS Active Server Pages monitors Tomcat Servlet monitors

IIS Web Service monitors Tomcat WebApp monitors

Sun Java System Web Server monitors

Open issues in BMC ProactiveNet Monitors


■ Deprecated monitors in the Administration Console

The Monitor Wizard interface in the Administration Console has been deprecated. The monitors that can be added using this interface have also been deprecated. They are:

Open issues in BMC ProactiveNet Monitors

This section provides information about problems that remain open for BMC ProactiveNet Monitors in this release.

Corrected issues for BMC ProactiveNet Monitors

The following problems were reported in earlier releases of the BMC ProactiveNet Monitors and have been corrected in this release.

Apache Web Server Pool monitors WebLogic Server Pool monitors

IIS Web Server Pool monitors WebSphere Pool monitors

Linux Server CPU Pool monitors Windows Server CPU Pool monitors

Solaris Server CPU Pool monitors

Script-based monitors File monitors

Resource Pool monitors Windows Management Instrumentation monitors

SNMP monitors Windows Performance Counter monitors

JMXTM monitors BMC VMware Adapter

Tracking ID Issue

Application Diagnostics is incorrectly displayed in the event rule wizard menu regardless of the monitor types filter.

Application Diagnostics data is attached only to events on monitor types that are supported for Application Diagnostics. If you select to run Application Diagnostics as the rule's action against a monitor that does not support Application Diagnostics, no results appear.

QM001690512 While creating an SQL VAM monitor, you cannot specify special characters in your SQL query.

QM001690900 If you are using the Windows Management Instrumentation (WMI) Wizard on Microsoft Windows 2008 R2 to create a custom monitor, start the BMC ProactiveNet Agent as a domain user having local administrator rights on the monitor device.

QM001667952 When creating Windows process monitors, the multi-byte characters in the command line match field are displayed as question marks (??).

BMC Impact Integration Web Services


BMC Impact Integration Web ServicesThis section provides information about new functionality, what’s changed, issues that have been resolved, and issues that remain open for BMC Impact Integration Web Services.

What’s new in BMC Impact Integration Web Services

■ Support for version 8.6.02 of BMC Impact Integration Web Services

For information about BMC Impact Integration Web Services, see the BMC Impact Integration Web Services Server Getting Started Guide.

■ BMC Impact Integration Web Services version 8.6.02 provides an mc_iiws.baroc file for client samples. It defines the IIWS_TEST_EV event and the IIWS_TEST_DATA data classes used in the BMC Impact Integration Web Services client sample programs.

To use the mc_iiws.baroc file:

1. Copy the file to the KB directory of the cell.

2. Add an entry for this file in the .load file in the KB directory of the cell.

3. Compile the KB for the cell:

1. Open a command prompt and change to the KB directory for the cell: MCELL_HOME\etc\<cell>\kb directory

2. From this directory, compile the KB by entering the following command: mccomp manifest.kb

4. Restart the cell.

■ BMC Impact Integration Web Services now logs version information, build number, and build date in the iiws.log file.

Tracking ID Issue

QM001680292 Resource Pool monitor instances do not collect data after the Jserver or BMC ProactiveNet server is restarted.

QM001658550 Windows monitors fail to collect data after the IP address for the BMC ProactiveNet server changes.

What’s changed in BMC Impact Integration Web Services


What’s changed in BMC Impact Integration Web Services

■ The SendEvent operation supports all of the following MessageTypes:

■ MSG_TYPE_NEW_EVENT

■ MSG_TYPE_MOD_EVENT |

■ MSG_TYPE_NEW_DATA

■ MSG_TYPE_MOD_DATA

■ MSG_TYPE_OVERWRITE_DATA

■ The QueryEvent operation supports the edelete command. The following are the two ways to define the edelete command:

■ edelete <Num> END

■ edelete <Class> ; { <SlotAssignC> } END

■ The QueryData operation supports the ddelete command. The following are the two ways to define the ddelete command:

■ ddelete <Num> END

■ ddelete <Class> ; { <SlotAssignC> } END

■ In the SendEvent API, for a new event, if the value of mc_arrival_time is not set, BMC Impact Integration Web Services sets the mc_arrival_time slot value.

Open issues and workarounds in BMC Impact Integration Web Services


Open issues and workarounds in BMC Impact Integration Web Services

The following topics provide information on issues that remain open in BMC Impact Integration Web Services.

Table 2 Open issues and workarounds in BMC II Web Services Server


The Tomcat server starts but cannot access web services. If the port number for the BMC II Web Services Tomcat is in use when you start the Tomcat server, you cannot access the web services web point. For example, when trying to access BMC II Web Services wsdl, the browser displays the following message: Page not found.

Workaround:

1. Check the catalina log.

2. Change to the following directory: $IIWS_HOME/Tomcat/logs

3. Search the latest catalina log for the following message:

Sep 24, 2010 11:16:57 AM org.apache.coyote.http11.Http11AprProtocol initSEVERE: Error initializing endpointjava.lang.Exception: Socket bind failed: [730048] Only one usage of each socket address (protocol/network address/port) is normally permitted. at org.apache.tomcat.util.net.AprEndpoint.init(AprEndpoint.java:646)at org.apache.coyote.http11.Http11AprProtocol.init(Http11AprProtocol.java:107)at org.apache.catalina.connector.Connector.initialize(Connector.java:1014)at org.apache.catalina.core.StandardService.initialize(StandardService.java:680)at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:795)at org.apache.catalina.startup.Catalina.load(Catalina.java:524)at org.apache.catalina.startup.Catalina.load(Catalina.java:548)at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)at java.lang.reflect.Method.invoke(Method.java:597)at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:261)at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)Sep 24, 2010 11:16:57 AM org.apache.catalina.startup.Catalina loadSEVERE: Catalina.start

This message indicates that the port IIWS tomcat using is not available For information about changing port numbers, see the BMC ProactiveNet Performance Mangement Web Services Getting Started Guide.

QM001533108 A root cause query initiated from the BMC II Web Services Server may return different results from what is displayed in the BMC Impact Explorer Services tab view. The results may differ based on the type of component and its status.

QM001535070 The setMaintenanceMode and setManualStatus requests of the BMC II Web Services Server client do not work with a high availability configuration in the event that a failover has occurred, meaning that the primary cell server is down.

Closed issues in BMC Impact Integration Web Services


Closed issues in BMC Impact Integration Web Services

The following topics provide information on issues that are fixed in this release of BMC Impact Integration Web Services.

BMC ProactiveNet CMDB Extensions and BMC Impact Model Designer

This section describes the issues that remain open and the issues that have been corrected.

QM001702702 For a string slot value inside square brackets, such as msg = '[This is a string slot]', when the object is queried from BMC II Web Services, BMC II Web Services returns the value as type string array and not string.

Table 3 Closed issues in BMC Impact Integration Web Services


QM001701562 If BMC IIWS failed to close the query to the cell at the endQuery call, the following error message was returned:

BMC-IMC101008E: Cannot handle unregistered client

QM001700904 The queryClassdefnition operation returned incorrect type for List type and Enumeration type slots.

QM001695898 The queryClassdefnition operation returned incorrect indexes for parents and children.

Table 2 Open issues and workarounds in BMC II Web Services Server


Open issues in BMC ProactiveNet and BMC Atrium CMDB integration


Open issues in BMC ProactiveNet and BMC Atrium CMDB integration


e

Tracking ID Issue

QM001714489 If you are installing BMC ProactiveNet CMDB Extensions on a system of a lower configuration, the installer may display a message that the BMC_PN: Atrium Explorer Plugin package failed to load.

Workaround: Run the BMC ProactiveNet CMDB Extensions installer once again.

QM001707695 If you have integrated BMC ProactiveNet with BMC Atrium CMDB and BMC BladeLogic or plan to integrate BMC ProactiveNet with BMC BladeLogic after upgrading to version 8.6.02, the UDDI credentials you provided for BMC Atrium CMDB are considered for both, BMC Atrium CMDB and BMC BladeLogic after the upgrade.

QM001675979 In BMC Atrium CMDB 7.6.03, publication fails when the ImpactDirection property of a published impact relationship component is changed.

Workaround:

Use the following procedure to publish the service model:

1. Delete the relationship from the cell by unflagging the impact of the relationship. Then promote and publish the service model.

2. Add the relationship with the changed direction to the cell by flagging the impact of the relationship again. Then promote and publish the service model once more.

QM001657751 If you are using BMC Atrium Explorer with BMC Atrium CMDB 7.6.02, and view a service model in BMC Impact Model Designer, the same service model appears to be reversed in the BMC ProactiveNet Operations Console.

SW00366605 The reconciliation standard job creation fails for the BMC.ADDM dataset with the midtier in BMC Atrium CMDB version 7.5 patch 5 with BMC ADDM version 8.1.

Workaround: Create a reconciliation job before installing the BMC ProactiveNet CMDB Extensions. You can use the BMC AR User tool to create reconciliation jobs. For information on creating reconciliation jobs, see the Atrium CMDB Normalization and Reconciliation Guide.

SW00378280 After deleting an impact relationship in BMC Impact Model Designer, if the relationship is created again, then the promotion of this relationship fails.

Workaround: For the impact relationship, mark the value of the MarkAsDeleted attribute to No in the BMC Remedy Action Request User tool. Then do the promotion again.

SW00380484 If you are using BMC Atrium CMDB version 7.6.0.3, no impacts are generated out-of-the-box for relationships created in BMC Atrium Explorer.

Workaround: Enable inline normalization manually on the sandbox dataset of BMC Atrium Explorer. For information about normalization, see the BMC Atrium CMDB 7.6.03 Normalization and Reconciliation Guide at http://webapps.bmc.com/support/faces/prodversion.jsp?prodverseqid=180459

Corrected issues in BMC ProactiveNet and BMC Atrium CMDB integration


Corrected issues in BMC ProactiveNet and BMC Atrium CMDB integration

The following problems were reported in earlier releases of the integration between BMC ProactiveNet and BMC Atrium CMDB and have been corrected in this release.

Integration for BMC Remedy Service DeskThis section provides information about the new functionality and the changes for this release.

What’s new in Integration for BMC Remedy Service Desk

The section describes new features in the Integration for BMC Remedy Service Desk (IBRSD) product.

Removal of slot restrictions

Earlier versions of IBRSD imposed a limitation of 2048 characters to pass from an event slot to any field in BMC Remedy AR System. This limitation has been removed in this version of IBRSD (version 7.4.01). That is, you can pass any number of characters from an event slot to a field in BMC Remedy AR System.


QM001638562 If you manually create a service in BMC ProactiveNet and you import a service from the BMC Atrium CMDB into BMC ProactiveNet that has the same name as the manually created service, two services with the same name are created; however, the Services tree in the BMC ProactiveNet Operations Console displays only one of the duplicate services.

QM001657896 If you have two or more CIs in the topology view and then you switch to the table view, and click the Edit button above the table, the Edit Component Properties dialog box is not displayed.

SW00375170 In the BMC ProactiveNet Operations Console, when your cross-launch a configuration item (CI) to CMDB using the Edit with Impact Model Designer option to edit a CI, the CI opens in the asset view in BMC Impact Model Designer. You cannot edit the CI in the asset view. To edit the CI, manually convert the asset view to sandbox view using the Quick Edit option.

SW00379013 When BMC ProactiveNet CMDB Extensions are upgraded from previous versions to version 7.6.03, installation of the extensions may fail.

SW00379678 The icons for the BMC_StorageSubSystem CI may appear to be different in BMC ProactiveNet and BMC Impact Model Designer.

Open issues and workarounds in IBRSD



The following issues remain open in this release of IBRSD. If a tracking ID has been assigned, it is provided.

Table 4 Open issues and workarounds in IBRSD (part 1 of 5)

Tracking ID Issue

QM001649942 The following error message is displayed in the ibrsd.trace log file when BMC Remedy AR System server is unable to send an update to an incident:

Error -110

This issue happens when the BMC Remedy AR System server loses connectivity to the BMC Impact Manager cell.

Workaround: Reconnect the BMC Remedy AR System server to the BMC Impact Manager cell.

QM001654123 IBRSD does not support incident creation for service models that have shadow configuration items (CIs).

QM001672741 When creating service impact management policy, if you use the default values for the SIM Priority to Incident Urgency and SIM Status to Incident Impact fields in the BMC Intelligent Incident Policy Configuration dialog box, an error message is displayed that states that there is a missing field and the status INFO is blank.

Workaround: Select to use custom values for the SIM Status to Incident Impact field and then set the global incident mappings as documented in the Integration for BMC Remedy Service Desk User Guide to override the default value.

QM001672740 When creating a service impact management policy, if you select the Company after you select the cell, class of CI, and components to include in the policy, the policy will not be created and related incidents will not get generated.

Workaround: Select the Company name before you set the other options in the BMC Intelligent Incident Service Policy Configuration dialog box. For details about policy creation, see the Integration for BMC Remedy Service Desk User Guide.



QM001680586 You cannot create an incident in IBRSD for the BMC_StorageSubsystem class. For configuration items (CIs) of this class, if you create an incident, the following error is displayed in the BMC ProactiveNet Operations Console:

ERROR NUM = 326. ERROR MESSAGE = Required field cannot be reset to a NULL value. APPENDED ERROR MESSAGE = HPD:Associations : Form Name01.ERROR NUM = 52. ERROR MESSAGE = The field is a core system field and cannot be changed. APPENDED ERROR MESSAGE = 15.ERROR NUM = 52. ERROR MESSAGE = The field is a core system field and cannot be changed. APPENDED ERROR MESSAGE = 6.ERROR NUM = 52. ERROR MESSAGE = The field is a core system field and cannot be changed. APPENDED ERROR MESSAGE = 5.ERROR NUM = 52. ERROR MESSAGE = The field is a core system field and cannot be changed. APPENDED ERROR MESSAGE = 3.ERROR NUM = 52. ERROR MESSAGE = The field is a core system field and cannot be changed. APPENDED ERROR MESSAGE = 1.

QM001534955 In a high-availability scenario, when the secondary cell becomes active, if the status of an incident in Remedy AR System changes, it does not reflect in the Notes tab for its corresponding incident information event in BMC IX. Even when the primary cell is active again, the Notes tab does not display the status change.

QM001573741 On a 64-bit Windows platform, the IBRSD ARS Module installation program, IBRSD_ARSWin.exe, fails or hangs.

Workaround:

1. From your Windows host, click Start, then click the Control Panel icon.

2. Double-click the System icon. The System Properties dialog box is displayed.

3. In the Performance area, click the Settings button. The Performance Options dialog box is displayed.

4. Select the Data Execution Prevention tab.

5. Select the Turn on DEP for essential Windows programs and services only option.

6. Click OK to accept the changes and close the Performance Options dialog.

7. Click OK to close the System Properties dialog.

8. Restart your Windows host.

9. Restart the installation program, IBRSD_ARSWin.exe.

QM001533927 In the Japanese locale, after successful installation and unsuccessful import of .arx files, if you tried to manually import the .arx files, the import is successful but IBRSD displays an error message.

Workaround: None needed. You can safely ignore the error message.


Tracking ID Issue



QM001575634 For some Topology Discovery components, incidents retry events are not created on the secondary cell.

QM001613794 EVENTS with a large amount of data in particular slots may result in an IBRSD failure.

Workaround: Nullify the contents of these slots while propagating to IBRSD using the gateway.ibrsd file.

For example, if you have a large amount of data in the mc_operations slot, you would modify the gateway.ibrsd file as follows:

add.new=[cell_name=$CNAME,mc_operation='']

You must restart the cell after any changes to the gateway.ibrsd file.

QM001639212 IBRSD sends events each time an incident is modified, even when none of the tracked values change.

QM001652319 I18N only. The IBRSD installation utility checks for a particular log with English text. If that text is returned in any other language, then the installation fails.

Workaround: The AR Module must be installed under the EN locale. After the installation has completed, you can change to a non-EN locale.

QM001657483 The following error message is displayed in the trace log when the msg slot is removed from gateway.ibrsd and defaultmapping.map for updated events:

WARNING: BiiARS: BMC-COM786133W: IMEVENT: Error -110 in getting slot msg

The msg slot is not used by the ITSM workflow for an updated event (only for a new event) so it should be possible to remove the msg slot from the gateway.ibrsd entries and the update map(s) in defaultmapping.map. However, when you do, this error is still displayed.

QM001616797 Installation of the IBRSD - AR System module fails with the following error message:

Error: Unable to get host name.Malformed \uxxxx encoding.

This error occurs if the ar.cfg file on the computer where the BMC Remedy Action Request System server is installed contains a forward slash \ or a lower case u in any parameters specified in the file.

Workaround: Edit the ar.cfg file to change the forward slash to a backward slash / or a lower case u to upper case before you install the IBRSD - AR System module.


Tracking ID Issue



QM001623770 The IBRSD service fails to start in BMC ProactiveNet 8.0.

Workaround:

1. Ensure that the IBRSD - AR System module is installed on the BMC Remedy AR System Server.

2. Configure IBRSD to connect to the BMC Remedy AR System Server by performing the following steps:

A. Navigate to $IBRSD_HOME/conf/.

B. Open ibrsd. conf and modify the following parameters:

■ ARSServerName■ ARSServerPortNum■ ARSServerUserName

3. Run the EncryptUtility utility from the IBRSD install directory as follows:

On UNIX:

./EncryptUtility -f $IBRSD_HOME/conf/ -l $IBRSD_HOME/log/ -p ARSystemUserPassword

On Windows:

EncryptUtility.exe -f %IBRSD_HOME%\conf\ -l %IBRSD_HOME%\log\ -p ARSystemUserPassword

For detailed instruction about configuring IBRSD, see the Integration for BMC Remedy Service Desk User Guide.


Tracking ID Issue

Corrected issues in IBRSD


Corrected issues in IBRSD

The following problems were reported in earlier releases of IBRSD and have been corrected in this release.

QM001623738 When you integrate a BMC Impact Manager cell with BMC Remedy IT Service Management (BMC Remedy ITSM) 7.6, BMC Atrium 7.6, and BMC Remedy AR System 7.5 patch 003 and generate an event by enabling the IBRSD policy, incident creation fails and the following message is displayed:

Error in Incident WorkFlow. ERROR NUM = 45974. ERROR MESSAGE = . APPENDED ERROR MESSAGE = You must associate a service item to this incident..

Workaround: In BMC Remedy AR User, perform the following steps to create an incident rule:

1. Go to Home Page =>Application Administration Console => Custom Configuration => Incident Management => Advanced Options => Rules.

2. In the Configure Incident Rule page, create an incident rule with the following settings:

■ Require Service CI Related On Submit = No■ Require CI Related On Resolved = No.

Table 5 Corrected issues in IBRSD

Tracking ID Issue

QM001685191 The Notes field in the IBRSD Retry event in the event view displayed he wrong timestamp.

QM001684808 The incident information event did not display the company name.

QM001677184 Incidents are created for events with a status of MAJOR and associated with a configuration item (CI), even though the IBRSD policy defines that incidents should be created for events with a status of CRITICAL only. Even if the incident with the CRITICAL event is resolved, the incidents with the MAJOR events remain open until they are also resolved even though they are of less severity than the original incident.

QM001605935 If the message slot of an event ends with a closing bracket (]), the resulting incident message in BMC Remedy Service Desk is not displayed.

QM001605548 Unable to duplicate an Intelligent Incident service policy through AR.


Tracking ID Issue

BMC ProactiveNet Publishing Server


BMC ProactiveNet Publishing ServerThe BMC ProactiveNet Publishing Server publishes a service model to the BMC ProactiveNet cell. It provides services to synchronize data from the BMC Atrium CMDB into the BMC ProactiveNet cell and the BMC ProactiveNet JServer. The Publishing Server performs the following functions:

■ automatically publishes the BMC Atrium CMDB service impact model to cells when any reconciliation job terminates

■ publishes the BMC Atrium CMDB service impact model to cells on demand

■ publishes data from a BAROC source file to cells on demand

■ exports the class definitions on demand to BAROC files that are ready for distribution to the BMC ProactiveNet cells

Open issues and workarounds in the BMC ProactiveNet Publishing Server


QM001577289 Unable to start an IBRSD instance using a BMC Remedy AR System Server password that starts with upper case or a special character.

QM001526195 If a CI in CMDB has pre-defined product categorization values and this CI is impacted, IBRSD creates an incident with the correct product categorization values. If you change these product categorization values and impact the CI before the initial incident is closed, IBRSD creates an update incident with the previously stored product categorization values instead of the changed values.

Table 6 Open issues and workarounds in BMC ProactiveNet Publishing Server (part 1 of 5)

Tracking ID Issue

QM001557676 While using mcell -id when the cell had published data, the issue Unique DataIdentifer already in Use occurred at publishing because with the -id the data was removed from mcdb but not from smdb.

QM001558169 If a CI with the same mc_udid is published, the directfeed component is overwritten and its state is not recovered. The component’s relationships are lost.

Table 5 Corrected issues in IBRSD

Tracking ID Issue



QM001609558 The procedure in the BMC ProactiveNet Service Modeling and Publishing Guide for how to enable an attribute for BMC ProactiveNet is incorrect.

Workaround: Use the corrected procedure under “Support for BMC ProactiveNet” on page 72.

QM001656992 The publication preview includes all configuration items (CIs) that have been modified in a attribute but should only include CIs that were modified in a SIM attribute.

QM001660881 When a publication filter is deleted from the BMC ProactiveNet Administration Console, but the corresponding publication fails, then the filter remains pending for deletion. A new filter with the same ID cannot be added until the one pending is deleted.

QM001663497 Sometimes, even though the Publishing Server is shut down gracefully, an e-mail message is sent alerting users that the Publishing Server has shut down abruptly.

QM001663912 For a selected filter in the BMC ProactiveNet Administration Console, you cannot view what has been published as part of the filter and what is pending for publication.

QM001667770 When publishing a large service model, the pshowlog displays the following message: Request timeout expired.

The Publishing Server remains busy and does not accept other requests.

Workaround: Restart the Publishing Server and view the XML request log directly, rather than retrieving it using the Publishing Server. Do not use pshowlog or plog, but run plogdisplay directly on the file from pserver's log directory.

QM001667803 The preview following a publication lists all the configuration items (CIs) that were added or moved to a different cell. The situation occurs because the HomeCell is set after publication and the Notification Engine returns all CIs modified in the HomeCell, although this is not a SIM attribute on the cell.

QM001668017 and QM001668247

The Publication History includes all requests. You cannot filter for publications only (QM001668017) or filter out publications that terminate with “Nothing is to be published” (QM001668247).

QM001670656 Uninstalling does not clear the BMC Action Remedy form entries used by pserver.

QM001671337 If the Publishing Server’s tmp directory (installDirectory\pw\server\tmp\pubSrvName for Windows, /usr/pw/server/tmp/pubSrvName for UNIX) is deleted, then an error occurs when the Publishing Server is restarted. For example:

\global\PN\pw\server\bin\pserver: \installDirectory\pw\server\tmp\ps_bppmprod\pserver.out: cannot create

Workaround: Recreate the tmp directory.

QM001671460 The pscontrol stop command does not stop the pserver service on Windows. Because of this, stopping the publishing server from the Services screen may not work.

Workaround: Stop the service or use the pw p e pserver command to stop the process. Execute pw p l to confirm stopping of the service. This is because stopping of the publishing server may take some time and the pw p e pserver command may be terminated before that.

QM001671504 Publication requests that have a result of NAK display in history with status Unknown.


Tracking ID Issue



QM001671531 With a non-C locale password, decoding of CMDBPassword by pserver may fail when pserver and pw commands are run in the same shell. The decoding of the password depends on the locale. Because pw commands set the C locale after running pw commands, the locale of the shell has changed.

Workaround: Do not mix pw commands and pserver command in the same shell. Always run pserver from a shell where no pw commands were run.

To encrypt the password according to the shell's locale, re-enter the password in the /pw/server/etc/pserver.conf file in plain text and restart pserver.

QM001671604 After upgrading multiple BMC ProactiveNet servers that are integrated with the same BMC Atrium CMDB, a publication filter is not created and BMC Atrium CMDB synchronization tasks are deleted. For upgrade from BMC ProactiveNet 8.0, the situation occurs only if different servers use the same name for the synchronization tasks.

Workaround: Employ the workaround for your situation:■ (upgrade from BMC ProactiveNet 7.7) Create a publication filters manually.■ (upgrade from BMC ProactiveNet 8.0) Before upgrading, ensure that all BMC Atrium

CMDB synchronization tasks are unique across all servers.

QM001672995 In a cluster environment, if the mcell process stops, then all processes are expected to restart in a secondary node. The pserver process might continue to run in the offline node if the mcell process stops during an ongoing publication.

Workaround: Avoid stopping pserver, and in particular switching the active node of a cluster setup while a publication is ongoing. To verify if a publication is ongoing, run publish -w. If a publication is ongoing this returns Request rejected by the Publishing Server: Another publish request is ongoing.

Wait 15 minutes or more, depending on the size of the ongoing publication, until pserver stops by itself. If it continues to run, then you may have to kill pserver process, then restart the pserver with the pw p s pserver command in the online node.

To ensure that all CIs are retrieved, run the publish command.

QM001675979 In BMC Atrium CMDB 7.6.03, publication fails when the ImpactDirection property of a published impact relationship component is changed.

Workaround: Use the following procedure to publish the service model:

1. Delete the relationship from the cell by unflagging the impact of the relationship. Then promote and publish the service model.

2. Add the relationship with the changed direction to the cell by flagging the impact of the relationship again. Then promote and publish the service model once more.


Tracking ID Issue



QM001675985 (Japanese locale, Solaris 10) The CMDBPassword property in the /pw/server/etc/pserver.conf might not be encrypted, even after the pserver is started.

Workaround:

Execute the following steps:

1. Download the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files, which include the following files:

■ local_policy.jar■ US_export_policy.jar

2. Copy the local_policy.jar and US_export_policy.jar files into the /usr/pw/jre/lib/security directory.

3. Restart pserver with the pw p s pserver command.

The password is now encrypted for the ja_JP.eucJP locale.

QM001680123 BMC ProactiveNet only supports one SIM cell. Distribution of a service impact model across multiple SIM cells is not supported. In the BMC ProactiveNet Administration Console and the BMC ProactiveNet Operations Console, you can only view the service impact model on the embedded SIM cell.

QM001680139 In the BMC Impact Model Designer component of BMC Atrium Explorer, you cannot view what is published and what is pending for publication.

QM001680147 Large impact graphs (with 10,000 objects or more) take more than five minutes to be processed by the BMC Atrium Notification Engine (NOE), also known as Query Result Differencer (QRD), and they fail with an AR filter remote procedure call (RPC) timeout.


Tracking ID Issue

Corrected issues in BMC ProactiveNet Publishing Server


Corrected issues in BMC ProactiveNet Publishing Server

The following problems were reported in earlier releases of the BMC ProactiveNet Publishing Server and have been corrected in this release.

SW00380486 If you are using BMC Atrium CMDB version 7.6.0.3 and BMC Atrium Discovery Dependency Mapping version 8.2, BMC Atrium Discovery Dependency Mapping does not create impact relationships. It relies on the auto impact feature of CMDB version 7.6.03. This feature is not enabled out-of-the-box.

Workaround: While installing BMC Atrium Discovery Dependency Mapping, set up a batch normalization job to run on the BMC.ADDM dataset. After BMC Atrium Discovery Dependency Mapping populates the data in the BMC.ADDM dataset, run batch job on the BMC.ADDM dataset. After the completion of batch normalization job, the impact model is available in BMC.ADDM. At this time, start a reconciliation job on BMC.ADDM to reconcile with the BMC.ASSET dataset. The reconciliation kicks off a new automated publication and the service model is synchronized in BMC ProactiveNet. For information about normalization, see the BMC Atrium CMDB 7.6.03 Normalization and Reconciliation Guide at http://webapps.bmc.com/support/faces/prodversion.jsp?prodverseqid=180459

SW00380488 If you are using BMC Atrium CMDB version 7.6.0.3 and a custom discovery tool that does not create impacts but relies on automated impact for impacts to be generated, then ensure that you run a normalization in the import dataset before reconciling it into the production dataset BMC.ASSET. If you run normalization from the BMC.ASSET dataset, this will not trigger an automated publication.

Workaround: Run normalization in the import dataset before reconciling into BMC.ASSET. Or, run a manual publication.

Tracking ID Issue

QM001535682 When the AR Notify plug-in is not loaded, a reconciliation job hangs and remains in a started status, causing following promotions and reconciliation jobs to hang.


Tracking ID Issue

Upgrades from BMC Impact Solutions


Upgrades from BMC Impact SolutionsThe following sections describe what’s new in upgrades from BMC Impact Solutions and also describe open issues while upgrading from BMC Impact Solutions to BMC ProactiveNet.

What’s new in upgrades from BMC Impact Solutions

■ BMC ProactiveNet Server 8.6.02 supports a direct upgrade from BMC Impact Solutions 7.1 through 7.4. Previously, BMC ProactiveNet Server 8.5.00 supported a direct upgrade from BMC Impact Solutions 7.2 and 7.3. BMC ProactiveNet 8.5.00 patch 1 added the support of a direct upgrade from BMC Impact Solutions 7.1.

■ You can upgrade directly from a 7.3.xx or 7.4 BMC Impact Solutions installation to a BMC ProactiveNet 8.6.02 Sybase or Oracle deployment. Previously, only the Sybase database was supported.

QM001651147 When the load on the BMC Remedy Action Request (AR) System server plug-in is very high, the system sometimes returns the following connection error in the Publication History window: The AR System Plug-In server is not responding (ERROR-8939).

QM001665204 The following information is missing from documentation:

In a BMC ProactiveNet Enterprise environment, only configuration items (CIs) that are assigned to the node's cell are published when the CIs are set to PublishToSIM (that is, set to Inherit, Yes and Propagate, or Yes in the BMC Impact Model Designer). To publish CIs that are assigned to another node's cell, set the top-level CI assigned to that node to Yes and Propagate.

For example, for the service model CI4 => CI3 => CI2 => CI1

where■ CI1 is assigned to cell A and set to Yes and Propagate■ CI2 is assigned to cell A and set to Inherit■ CI3 is assigned to cell B and set to Inherit■ CI4 is assigned to cell B and set to Inherit

CI3 and CI4 are not published. To publish the CIs, set CI3, which is the top-level CI assigned to cell B, to Yes and Propagate.

Tracking ID Issue

Special KB migration instructions: BMC ProactiveNet 8.0 or 8.1


■ You can use the 8.6.02 KB Migration Wizard to merge your current KB definitions with the latest standard 8.6.02 KB definitions and formats. The KB Migration Wizard supports the following KB migration paths:

■ BMC Event and Impact Management 7.1 through 7.4 KB definitions to the 8.6.02 standard KB

■ BMC ProactiveNet 8.5, 8.5.xx, or 8.6.01 KB definitions to the 8.6.02 standard KB

You execute the KB Migration Wizard from a BMC ProactiveNet Agent system. See the BMC ProactiveNet Upgrade Guide for more information.

■ BMC ProactiveNet 8.0 or 8.1 users who intend to upgrade to BMC ProactiveNet Server 8.6.02 must follow special instructions to migrate the 8.0 or 8.1 KB to the latest 8.5 patch version KB before continuing the upgrade to 8.6.02. See “Special KB migration instructions: BMC ProactiveNet 8.0 or 8.1.”

■ BMC ProactiveNet Analytics 7.7 users who have a separate BMC Event and Impact Management 7.xx implementation cannot upgrade directly to 8.6.02. Instead they first upgrade to the latest patch version of the 8.5.xx server using the -hybrid option. Next, they must follow special instructions to migrate the BMC Event and Impact Management 7.xx KB to the latest 8.5 patch version KB. Then they can continue with the upgrade process. See “Corrected server upgrade and KB migration sequence: BMC ProactiveNet Analytics 7.7 hybrid upgrade” on page 61.


BMC ProactiveNet 8.0 or 8.1 users who wish to upgrade to BMC ProactiveNet Server 8.6.02 must execute a sequence of KB migrations and server upgrades.

1. Use the 8.6.02 mmigrate utility from the command line to migrate the 8.0 or 8.1 KB to the latest standard 8.5 patch KB.

2. Upgrade the 8.0 or 8.1 server to the latest 8.5 server version.

3. Use the 8.6.02 KB Migration Wizard to migrate the latest 8.5 patch KB to the 8.6.02 standard KB.

4. Upgrade the latest 8.5 server version to BMC ProactiveNet Server 8.6.02.

(For more details about the overall upgrade sequence and the mmigrate utility, refer to BMC ProactiveNet Upgrade Guide.)

NOTE These KB migration instructions are in effect only until patch 3 of BMC ProactiveNet 8.5 is made available. The patch 3 technical bulletin will describe the simplified KB migration procedure.



The following guidelines address phase 1 of this sequence: using the 8.6.02 mmigrate utility to migrate the 8.0 or 8.1 KB to the latest standard 8.5 patch KB.

Windows

1 Save the 8.0 or 8.1 version of your environment variables PATH and MCELL_HOME, as in the examples below:

set M81=%MCELL_HOME%

set P81=%PATH%

2 Download the core component distributions for both the latest 8.5 patch and 8.6.02, noting the download directory.

3 Assign the following environment variables based on the download directory you specified. In the following examples, C:\Downloads is the specified directory.

set M85=C:\Downloads\8.5\MigrateKB\server

set M86=C:\Downloads\8.6.02\MigrateKB\server

4 Define a special merge directory to store the migrated KBs.

set MERGED=%M81%\mergedKB\server\etc

mkdir “%MERGED%”

The ..\mergedKB\server\etc file path is the temporary location of the migrated KBs. The mmigrate utility outputs the merged KB and places it in the temporary location. The server upgrade script prompts you for the special merge directory so that the routine can copy the migrated KB from the temporary location to the appropriate file path on the server.

5 Set the environment variables to use the 8.6.02 version of mmigrate:

set MCELL_HOME=%M86%

set PATH=%M86%\bin;%P81%

6 Execute the mmigrate utility from the command line.

NOTE The code snippets refer to “81,” representing the version number. You can substitute “80” if applicable.



A Change directory to the file path of the KB that you are migrating:

cd %M81%\etc

B Execute the mmigrate command with the appropriate options, as in this example:

mmigrate –bmc %M85%\etc\default\Admin\kb –aa elk_admin “%MERGED%\elk_admin”

Explanation: A reference KB has the latest definitions with which you are merging. mmigrate overrides the default for the reference KB through the -bmc parameter.

To illustrate, when migrating an administrative cell, use the latest 8.5 patch Admin KB as the reference KB (default\Admin\kb in the syntax example above) with the mmigrate -aa option. In the above example, elk_admin is the 8.0 or 8.1 Admin KB you are migrating.

When you use the other mmigrate options (-ae, -ap, or -as), the reference KB is the latest 8.5 patch standard KB (default\standard\kb in the syntax below). If migrating your standard 8.0 or 8.1 KB, say it’s named elk_sim, to the latest 8.5 patch KB, your mmigrate syntax would look as follows:

cd %M81%\etc

mmigrate –bmc %M85%\etc\default\standard\kb –as elk_sim “%MERGED%\elk_sim”

7 Use the 8.5 compiler to compile the migrated KBs.

A Define your 8.5 environment settings:



B Change to your merge directory and execute the mccomp command to compile the specified KB:

cd %MERGED%

mccomp elk_sim\kb\manifest.kb

8 Validate the KB using your standard test cases, and then continue with the server upgrade to the latest 8.5 version.



UNIX

1 Save the 8.0 or 8.1 version of your environment variables PATH and MCELL_HOME, as in the examples below:

export M81=”$MCELL_HOME”

export P81=”$PATH”


3 Assign the following environment variables based on the download directory you specified. In the following examples, $PWD is the specified directory.

export M85=”$PWD/8.5/MigrateKB/server”

export M86=”$PWD/8.6.02/MigrateKB/server”


export MERGED=”$M81/mergedKB”

mkdir –p “$MERGED”

The ../mergedKB/server/etc file path is the temporary location of the migrated KBs. The mmigrate utility outputs the merged KB and places it in the temporary location. The server upgrade script prompts you for the special merge directory so that the routine can copy the migrated KB from the temporary location to the appropriate file path on the server.


export MCELL_HOME=”$M86”

export PATH=”$M86/bin:$P81”

NOTE The code snippets refer to “81,” representing the version number. You can substitute “80”if applicable.





cd “$M81/etc”


mmigrate –bmc “$M85/etc/default/Admin/kb” –aa elk_admin “$MERGED/elk_admin”


To illustrate, when migrating an administrative cell, use the latest 8.5 patch Admin KB as the reference KB (default/Admin/kb in the syntax example above) with the mmigrate -aa option. In the above example, elk_admin is the 8.0 or 8.1 Admin KB you are migrating.

When you use the other mmigrate options (-ae, -ap, or -as), the reference KB is the latest 8.5 patch standard KB (default/standard/kb in the syntax below). If migrating your standard 8.0 or 8.1 KB, say it’s named elk_sim, to the latest 8.5 patch KB, your mmigrate syntax would look as follows:

cd “$M81/etc”

mmigrate –bmc “$M85/etc/default/standard/kb” –as elk_sim “$MERGED/elk_sim”






cd “$MERGED”

mccomp elk_sim/kb/manifest.kb


Corrected server upgrade and KB migration sequence: BMC ProactiveNet Analytics 7.7 hybrid upgrade


Corrected server upgrade and KB migration sequence: BMC ProactiveNet Analytics 7.7 hybrid upgrade

The “hybrid” upgrade refers to the upgrade of BMC ProactiveNet Analytics 7.7 with a separate BMC Event and Impact Management 7.xx implementation on a different host system.

The upgrade sequence described in the BMC ProactiveNet Upgrade Guide is incorrect. The corrected server upgrade and KB migration sequence is outlined in Table 7 on page 61.

Table 7 Main upgrade stages of BMC ProactiveNet Analytics 7.7 with BMC Event and Impact Management 7.xx implementation to 8.6.02

Stage Description Reference

1 Upgrade BMC ProactiveNet Analytics to the latest 8.5 patch version (8.5.xx), currently patch 2 (8.5.00.02). Use the -hybrid option.

(BMC ProactiveNet Analytics does not have a cell to migrate.)

See the server upgrade procedures (-hybrid switch) in Chapter 4 of BMC ProactiveNet Upgrade Guide.

2 Migrate the 7.xx BMC Event and Impact Management KB to the latest 8.5 patch version KB. Follow the special 8.6.02 mmigrate instructions.

See “Special KB migration instructions for hybrid upgrade: BMC Event and Impact Management 7.xx” on page 62.

3 Launch the pre-upgrade and upgrade wizards to port the BMC Event and Impact Management data to BMC ProactiveNet Server 8.5.xx.

After launching the BMC Event and Impact Management upgrade wizard tool, at the Step 8 of 10 screen, select the From ProactiveNet 7.7 to BPPM 8.5 option under the What type of Migration are you doing? heading.

See Chapter 2 of the BMC ProactiveNet Upgrade Guide.

4 Migrate the latest 8.5 patch version KB with the standard 8.6.02 KB using the 8.6.02 KB Migration Wizard.


5 Upgrade the BMC ProactiveNet 8.5.xx Server to the 8.6.02 Server.


Special KB migration instructions for hybrid upgrade: BMC Event and Impact Management 7.xx



In a hybrid upgrade of BMC ProactiveNet Analytics 7.7, follow these guidelines to migrate the BMC Event and Impact Management 7.xx KB to the latest standard 8.5 patch KB. You perform this migration by executing the 8.6.02 version of the mmigrate utility from the command line.

Windows

1 Save the 7.xx version of your environment variables PATH and MCELL_HOME, as in the examples below:

set M0=%MCELL_HOME%

set P0=%PATH%


3 Assign the following environment variables based on the download directory you specified. In the following examples, C:\Downloads is the specified directory.

set M85=C:\Downloads\8.5\MigrateKB\server

set M86=C:\Downloads\8.6.02\MigrateKB\server

NOTE These KB migration instructions are in effect only until patch 3 of BMC ProactiveNet 8.5 is made available. The patch 3 technical bulletin will describe the simplified KB procedure.

NOTE The code snippets refer to “0,” representing the 7.xx version number. You can substitute another value.




set MERGED=%M0%\mergedKB\server\etc

mkdir “%MERGED%”

The ..\mergedKB\server\etc file path is the temporary location of the migrated KBs. The mmigrate utility outputs the merged KB and places it in the temporary location. The server upgrade script prompts you for the special merge directory so that the routine can copy the migrated KB from the temporary location to the appropriate file path on the server.






cd %M0%\etc


mmigrate –bmc %M85%\etc\default\Admin\kb –aa elk_admin “%MERGED%\elk_admin”


To illustrate, when migrating an administrative cell, use the latest 8.5 patch Admin KB as the reference KB (default\Admin\kb in the syntax example above) with the mmigrate -aa option. In the above example, elk_admin is the 7.xx Admin KB you are migrating.

When you use the other mmigrate options (-ae, -ap, or -as), the reference KB is the latest 8.5 patch standard KB (default\standard\kb in the syntax below). If migrating your standard 7.xx KB, say it’s named elk_sim, to the latest 8.5 patch KB, your mmigrate syntax would look as follows:

cd %M0%\etc

mmigrate –bmc %M85%\etc\default\standard\kb –as elk_sim “%MERGED%\elk_sim”








cd %MERGED%

mccomp elk_sim\kb\manifest.kb


UNIX

1 Save the 7.xx version of your environment variables PATH and MCELL_HOME, as in the examples below:

export M0=”$MCELL_HOME”

export P0=”$PATH”


3 Assign the following environment variables based on the download directory you specified. In the following examples, $PWD is the specified directory.

export M85=”$PWD/8.5/MigrateKB/server”

export M86=”$PWD/8.6.02/MigrateKB/server”

NOTE The code snippets refer to “0,” representing the 7.xx version number. You can substitute any value.




export MERGED=”$M0/mergedKB”

mkdir –p “$MERGED”

The ../mergedKB/server/etc file path is the temporary location of the migrated KBs. The mmigrate utility outputs the merged KB and places it in the temporary location. The server upgrade script prompts you for the special merge directory so that the routine can copy the migrated KB from the temporary location to the appropriate file path on the server.






cd “$M0/etc”


mmigrate –bmc “$M85/etc/default/Admin/kb” –aa elk_admin “$MERGED/elk_admin”


To illustrate, when migrating an administrative cell, use the latest 8.5 patch Admin KB as the reference KB (default/Admin/kb in the syntax example above) with the mmigrate -aa option. In the above example, elk_admin is the 7.xx Admin KB you are migrating.

When you use the other mmigrate options (-ae, -ap, or -as), the reference KB is the latest 8.5 patch standard KB (default/standard/kb in the syntax below). If migrating your standard 7.xx KB, say it’s named elk_sim, to the latest 8.5 patch KB, your mmigrate syntax would look as follows:

cd “$M0/etc”

mmigrate –bmc “$M85/etc/default/standard/kb” –as elk_sim “$MERGED/elk_sim”


Open issues with upgrades from BMC Impact Solutions to BMC ProactiveNet






cd “$MERGED”

mccomp elk_sim/kb/manifest.kb


Open issues with upgrades from BMC Impact Solutions to BMC ProactiveNet


Upgrading in virtualization environmentsIf you are monitoring a virtual environment using VSM KM version 2.9.50 or earlier with BMC PATROL Agent version 3.8.50 or earlier and BMC ProactiveNet Server version 8.5, perform the following steps to upgrade to BMC ProactiveNet version 8.6.02:

1 Before the upgrade, edit the adapter instance and schedule the next auto discovery to the next day (so that no auto discovery is scheduled during the upgrade).

2 Upgrade the BMC ProactiveNet Server, BMC ProactiveNet Agent, and the BMC PATROL agents. For information about performing these upgrades, see the BMC ProactiveNet Upgrade Guide.

3 Check that all components are up and running after the upgrade.

Table 8 Open issues in BMC ProactiveNet Impact Solutions

Tracking ID Issue

QM001690280 You must remove special characters from Event group folder names before upgrading BMC Impact Solutions 7.x to BMC ProactiveNet 8.5.x and later.

BMC ProactiveNet Performance Management Triage and Remediation solution


If duplicate devices and groups are present, invoke the cleanup script to delete the duplicates. To do this:

A Open a BMC ProactiveNet command window or shell.

B Execute the following commands:

■ runjava apps.cmd.ObjectCleanUp -action delete-devices

■ runjava apps.cmd.ObjectCleanUp -action delete-async-emptygroups

The cleanup script deletes only the auto synchronized but empty devices and groups. For information about other parameters, execute the -help option.

4 After an hour, edit the adapter instance and schedule the auto discovery to every 15 minutes.

5 Perform a manual synchronization after 1 hour or wait for one more synchronization after 96 polls to make sure all instances and devices are updated correctly.

BMC ProactiveNet Performance Management Triage and Remediation solution

The Triage and Remediation solution is a BMC Atrium Orchestrator runbook component that launches triage and remediation workflows. These workflows can be triggered by events that are received from BMC ProactiveNet Performance Management. For more information about the Triage and Remediation solution, see the BMC ProactiveNet Performance Management Triage and Remediation Solution Getting Started Guide available on the Customer Support site.

Open issues and workarounds in the Triage and Remediation solution

The following issues remain open in this release of the Triage and Remediation solution. If a tracking ID has been assigned, it is provided.

Documentation corrections and clarifications


Documentation corrections and clarifications

The following corrections and clarifications are noted for the October 2010 release of the BMC ProactiveNet Performance Management Triage and Remediation Solution Getting Started Guide.

Do not perform Step 1 of the “Configure the ProactiveNet server cell” procedure under the topic heading “Configure BMC ProactiveNet for the Triage and Remediation solution.” Begin the procedure with the current Step 2 instead. (See page 39 of the PDF rendition.)

See Step 3c of the “Configure the BMC Atrium Orchestrator BMC Event Management and ProactiveNet monitor and actor adapters” procedure (page 42 of the PDF rendition). In the code example, ProactiveNetcell is a variable that refers to the actual name of the BMC ProactiveNet cell in your environment. Use the actual name of the BMC ProactiveNet cell.

Under Step 4 of the “Configure the BMC Atrium Orchestrator BMC Event Management and ProactiveNet monitor and actor adapters” procedure, the variable cellName in the code example also refers to the actual name of the BMC ProactiveNet cell in your environment, just as in Step 3c. Use the actual name of the BMC ProactiveNet cell.

In Table 13, “Adapter configurations parameters and nodes,” on page 49 of the PDF rendition, note the following clarifications:

■ For the BMC Event Manager and ProactiveNet monitor adapter, the gateway-name value in the code example should read BEMGW to be consistent with earlier examples.

Table 9 Open issues and workarounds in the Triage and Remediation solution

Tracking ID Issue

QM001664839 The DB Tablespace Full workflow in the Triage and Remediation solution does not execute. This is because the tsm entry is missing in the <MCELL_HOME>\etc\cellName\kb\rules\.load file.

Workaround:

1. Open the <MCELL_HOME>\etc\cellName\kb\rules\.load file.

2. Add the tsm entry to this file.

For more information about adding the tsm entry, see the BMC ProactiveNet Performance Management Triage and Remediation Solution Getting Started Guide.

ISS03792815 The instructions for configuring BMC ProactiveNet cells for the Triage and Remediation solution need corrections and clarifications. See “Documentation corrections and clarifications” on page 68.

BMC ProactiveNet documentation errata


■ For the BMC Event Manager and ProactiveNet actor adapter, the cell-name value in the code example is a reference to the actual name of the BMC ProactiveNet cell in your environment, as described in Steps 3c and 4 above. Use the actual name of the BMC ProactiveNet cell.

BMC ProactiveNet documentation errataThe following issues remain open in this release of the BMC ProactiveNet online Help and other BMC ProactiveNet documentation.

Table 10 Open issues in the BMC ProactiveNet online Help

Tracking ID Issue

QM001714365 The ‘Supported versions of BMC products required to use IBRSD’ section in the BMC ProactiveNet Compatibility and Support Matrix does not list BMC Remedy Action Request System versions 7.5 patch 005 and 7.6 patch 2 as supported versions. BMC Remedy Action Request System versions 7.5 patch 005 and 7.6 patch 2 are also supported in addition to the other versions mentioned in the section.

QM001712680 The BMC ProactiveNet Getting Started Guide on the Documentation CD is missing a command line option to install the BMC ProactiveNet Server on an Oracle database.

To use BMC ProactiveNet on Oracle:

1. Set up your Oracle environment. For more information about this, see the BMC ProactiveNet Getting Started Guide.

2. Download the BMC ProactiveNet installer and navigate to the setup.exe or setup.sh file.

3. Open a command prompt and execute the following command:

For Microsoft Windows: setup.exe -DCUSTOMDB=oracle

For Solaris: setup.sh -DCUSTOMDB=oracle

4. Follow the instructions in the “Installing BMC ProactiveNet Performance Management with Oracle” section of the BMC ProactiveNet Getting Started Guide.

BMC ProactiveNet documentation errata


QM001712519 The steps in the ‘Creating dependencies for BMC ProactiveNet Server cluster resource‘ section, ‘To create dependencies for Windows cluster 2008’ sub-section in the BMC ProactiveNet Getting Started Guide are inaccurate.

To create dependencies for Windows cluster 2008:

1. Stop the BMC ProactiveNet Server using the pw system stop command.

2. Go to Start =>All Programs => Administrative Tools => Failover Cluster Manager and click on the cluster name.

3. Scroll down to Cluster Core Resources section, right-click PnService and click Properties.

4. In the PnService Properties dialog box, click the Dependencies tab.

5. Click Insert to add a resource.

6. From the Resource drop-down list, select a cluster name and click Insert.

7. Select the cluster resource with the ‘AND’ option. Similarly, add all the resources.

8. Click Apply and OK.

9. Restart the BMC ProactiveNet Server using the pw system start command.

QM001710473 Online Help for the BMC ProactiveNet Administration Console does not launch on UNIX systems.

Workaround:

1. Check your system to determine the directory in which the Netscape executable is installed.

2. Ensure that the Netscape executable launches the browser after executing it through command line.

3. Open the <install_directory>/pw/pronto/bin/netscape.csh file.

4. Check the set NETSCAPE parameter and ensure that it points to the path where the Netscape executable is installed.

For example, if Netscape is installed at /usr/dt/bin, change the value of the set NETSCAPE parameter to /usr/dt/bin/netscape.

5. If Mozilla Firefox is installed instead of Netscape, change the value of the set NETSCAPE parameter to /usr/bin/firefox.

QM001699446 Search results on the Search tab may appear twice.

QM001674184 Context-sensitive Help for the Associate Monitors dialog box does not work. For information about associating monitors, see the BMC ProactiveNet Administration Guide.

QM001669588 On Mozilla Firefox, the Hide Contents icon in the BMC ProactiveNet Help may not work as expected.

Tracking ID Issue

Updates to the pw group add_subgroup section in the BMC ProactiveNet Command Line Reference Guide


Updates to the pw group add_subgroup section in the BMC ProactiveNet Command Line Reference Guide

The pw group add_subgroup section in the BMC ProactiveNet Command Line Reference Guide states that this command allows you to add subgroups (or child groups) to an existing parent group.

Ensure that both the parent group and the child group exist before executing the pw group add_subgroup command.

Downloading from the webThis section contains instructions for downloading from the BMC Software Electronic Product Download (EPD) web page.

Before you begin

You need logon credentials for the EPD web page. If you do not have logon credentials, go to https://webapps.bmc.com/signon/content/logon.jsp, and then click the Register Now link.

To download the selected product components from the web

1 Create a temporary directory on your computer for the product installation files.

2 Go to the EPD web page at https://webapps.bmc.com/signon/content/logon.jsp.

3 Enter your user name and password, and then click Submit.

4 Click Download Product.

5 On the Export Validation & License Terms page, provide the required information under Export Validation and License Terms sections.

6 Scroll to the bottom of the Export Compliance Disclaimer and TRIAL AGREEMENT panes, and click I Agree.

7 Click Continue.

https://webapps.bmc.com/signon/content/logon.jsp

https://webapps.bmc.com/signon/content/logon.jsp

Support for BMC ProactiveNet


8 In the Select Product page, select the BMC ProactiveNet Performance Management product and click Continue.

9 On the Select Product Version page, select BMC ProactiveNet Performance Management <version_number> for your associated platform and then click Continue.

You can filter the list of products by language and platform if too many entries appear.

10 On the Download Files page, click the BMC ProactiveNet <version_number> link and download the file to the temporary directory that you created in step 1.

For installation instructions, see the BMC ProactiveNet Getting Started Guide.

Support for BMC ProactiveNetThis section provides information about

■ documents that support the solution■ how to obtain the latest information about the solution■ how to obtain the solution■ how to contact Customer Support

NOTE The products listed in the selection pane are based on the support IDs that are associated to your account. If you do not see the product you want to download, click MANAGE SUPPORT IDS to add a valid support ID and password.

NOTE BMC ProactiveNet Analytics version 7.7 is on limited support.

Solution documents


Solution documents

The following documents support the solution:

■ BMC ProactiveNet Getting Started Guide ■ BMC ProactiveNet Deployment Guide **■ BMC ProactiveNet Upgrade Guide ■ BMC ProactiveNet Administrator Guide ■ BMC ProactiveNet User Guide ■ BMC ProactiveNet Data Adapter and Monitor Guide■ BMC ProactiveNet Troubleshooting Guide *■ BMC ProactiveNet Command Line Interface Reference Guide■ BMC Knowledge Base Development Reference Guide *■ BMC Impact Event Adapters User Guide *■ Integration for BMC Remedy Service Desk User Guide■ BMC ProactiveNet Service Modeling and Publishing Guide *■ BMC Impact Integration for Web Services Server Getting Started Guide■ BMC Impact Integration Web Services Developer Guide■ BMC ProactiveNet Performance Management Triage and Remediation Solution Getting

Started Guide *■ BMC ProactiveNet Performance Management Support and Compatibility Matrix■ BMC ProactiveNet Performance Management Disaster Recovery Best Practices Guide for

Sybase **■ BMC ProactiveNet Performance Management Disaster Recovery Best Practices Guide for

Oracle **■ BMC ProactiveNet Performance and Scalability Guide **■ BMC ProactiveNet online Help

NOTE Guides marked with an * have not been updated for BMC ProactiveNet version 8.6.02. Guides marked with ** will be released a few days after the General Availability (GA) date.

NOTE Information found in the books is more recent than information in the online Help. In case of conflicting information, the books take precedence.

Full-text search of solution documents


Full-text search of solution documents

BMC ProactiveNet includes a large documentation set in PDF format. With Adobe Reader version 7.0 and later, you can perform a full-text search across all of the PDF files that reside in the same directory, including subdirectories. If you do not have Adobe Reader version 7.0 or later, download the latest Adobe Reader version from http://www.adobe.com for free.

To search for a word or phrase in the BMC ProactiveNet PDF documentation:

1 Copy all the PDF files you want to search to a single directory.

The BMC ProactiveNet documentation PDF files are available from:

■ the BMC Software electronic product download (EPD) site as a .zip file■ the documentation CD found in the physical kit■ the BMC Software Customer Support site on the product page

2 Start Adobe Reader.

3 Click the search icon (binoculars) in the toolbar.

4 If the search icon is missing, right-click the toolbar to find more toolbar options.

Different versions of Adobe Reader put the option in different places.

5 After the Search window is displayed, select All PDF Documents in under Where would you like to search?

6 Click the folder selection box and choose Browse for Location.

7 Browse to the top-level folder that contains the PDF documents.

8 Type a search term in the What word or phrase would you like to search for? box and click Search.

The search tool searches for the term you entered in all of the PDFs in the chosen directory and its subdirectories and displays the results.

Where to view the latest solution information

The latest solution information is available on the Customer Support website at http://www.bmc.com/support_home.


http://www.adobe.com

How to obtain the solution


From the Customer Support site, you can perform several tasks, including

■ viewing the latest solution documentation (manuals, release notes, flashes, technical bulletins, online Help, and parameter information)

■ subscribing to proactive alerts to receive e-mail messages that inform you of new release notes, flashes, and technical bulletins for your products

■ searching for existing solution resolutions and frequently asked questions (FAQs)

How to obtain the solution

BMC ProactiveNet is available for download from the BMC Electronic Product Distribution (EPD) website at http://webapps.bmc.com/epd. Use the user name and password that your BMC sales representative gave you.

If you do not have a current license for the product, contact a BMC sales representative by calling 800 793 4262. If you cannot download the product, contact a sales representative and ask for a physical kit to be shipped to you.

Customer support

If you have problems with or questions about a BMC product, see the Customer Support website at http://www.bmc.com/support_home. You can view or download product documents, find answers to frequently asked questions, and download products and maintenance. If you do not have access to the web and you are in the United States or Canada, contact Customer Support at 800 537 1813. Outside the United States or Canada, contact your local BMC office or agent.

TIP If you do not already have a user name and password that allow you to fully access the Customer Support website, you can register for a user name and password on the site.

NOTE For download instructions, see the BMC ProactiveNet Performance Management Release Notes, also available on the EPD site.


http://webapps.bmc.com/epd

Customer support


© Copyright 2011 BMC Software, Inc.

ProactiveNet, ProactiveNet Logo and all other ProactiveNet trademarks and registered trademarks, including, but not limited to, Intelligent Threshold, SmartFilters, Intelliscope, ProactiveAgent, and ProactiveServer, are the exclusive properties of ProactiveNet Inc., a wholly-owned subsidiary of BMC Software, Inc. in the U.S.A and/or other countries.

Protected by U.S.Patents.

BMC ProactiveNet is subject to the terms detailed in the license agreement accompanying it. For more info on ProactiveNet, see www.bmc.com. For any support related query please refer to http://www.bmc.com/info_center_support/overview/0,3252,19097_45424060,00.html

You can also get help with BMC ProactiveNet using the contact details provided with your agreement.

© 1997 - 2011 ProactiveNet, Inc., a wholly-owned subsidiary of BMC Software, Inc.

BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other BMC trademarks, service marks, and logos may be registered or pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are the property of their respective owners.

AIX is the trademark or registered trademark of International Business Machines Corporation in the United States, other countries, or both.

IT Infrastructure Library® is a registered trademark of the Office of Government Commerce and is used here by BMC Software, Inc., under license from and with the permission of OGC.

ITIL® is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office, and is used here by BMC Software, Inc., under license from and with the permission of OGC.

Linux is the registered trademark of Linus Torvalds.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

UNIX is the registered trademark of The Open Group in the US and other countries.

BladeLogic and the BladeLogic logo are the exclusive properties of BladeLogic, Inc. The BladeLogic trademark is registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other BladeLogic trademarks, service marks, and logos may be registered or pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are the property of their respective owners.

All other trademarks or registered trademarks are the property of their respective owners.

BMC Software considers information included in this documentation to be proprietary and confidential. Your use of this information is subject to the terms and conditions of the applicable End User License Agreement for the product and the proprietary and restricted rights notices in the product documentation.

BMC SOFTWARE INC2101 CITYWEST BLVD, HOUSTON TX 77042-2827, USA• 713 918 8800Customer Support: 800 537 1813 (United States and Canada) or contact your local support center

proactivenet release notes

Documents

overview of bmc proactivenet

bmc bladelogic

bmc patrol

bmc proactivenet3new

bmc software

bmc proactivenetversion

bmc remedy service desk

closed issues