Skip navigation
Share This:

Are you searching the BMC Support Knowledge Base and getting too many results for products you are not using?

 

Are you spending time having to unselect/select various products in the list?

 

Would you like to search the BMC Support Knowledge Base and only see results for TrueSight Reporting and other Reporting components? For example, if you are using the product predecessor, see results which include ProactiveNet Reporting. Perhaps you are interested in seeing results for BMC Performance Manager Reporting articles?

 

If answer to any of the above is YES then you need to use a pre-filtered URL for those specific products:

 

Pre-filtered for:

TrueSight Operations Management Reporting

TrueSight Reporting

ProactiveNet Performance Management Reporting

ProactiveNet Reporting

BMC Performance Management Reporting

BMC Performance Manager Reporting

 

NOTE:

You will need to be already logged into BMC Support Central for this URL to work correctly.

Share This:

Are you searching the BMC Support Knowledge Base and getting too many results for products you are not using?

 

Are you spending time having to unselect/select various products in the list?

 

Would you like to search the BMC Support Knowledge Base and only see results for just BMC Performance Manager Portal or are you interested in either the BMC Performance Manager Express monitoring solutions as well as the Portal, or just the monitoring solutions?

 

If answer to any of the above is YES then you need to use a pre-filtered URL just for those products:

 

Pre-filtered for BMC Performance Manager Portal

Pre-filtered for BMC Performance Manager Portal and BMC Performance Manager Express solutions

Pre-filtered for BMC Performance Manager Express Solutions

 

NOTE:
You will need to be already logged into BMC Support Central for these URL's to work correctly

Share This:

Are you searching the BMC Support Knowledge Base and getting too many results for products you are not using?

 

Are you spending time having to unselect/select various products in the list?

 

Would you like to search the BMC Support Knowledge Base and only see results for just TrueSight/ProactiveNet or if you using these product predecessors, see results for just BEM/SIEM?

 

If answer to any of the above is YES then you need to use a pre-filtered URL just for those products:

 

Pre-filtered for TrueSight/ProactiveNet

 

Pre-filtered for BEM/SIEM

 

NOTE:

You will need to be already logged into BMC Support Central for these URL's to work correctly

Share This:

Hi everyone!

 

Our next installment of our Connect with BMC Performance Manager Portal Webinar Series will be held on May 10, 2016 at 10 am Central time to 12 pm Central time

 

The topics of this Webinar will include:

Security Vulnerabilities, Oracle 12c Support, Portal Diagnostics

 

Please make plans to plans to attend!

 

We'll be sending out Webinar registration details about 2 weeks before, so be on the lookout for the invitation. We look forward to working with you!

 

 

 

 

Performance Manager Portal: Security Vulnerabilities, Oracle 12c Support, Portal Diagnostics

Share This:

You have probably heard of the Heart-bleed, the Poodle, the Ghost, the LogJam, and the Freak vulnerabilities as they are often referred to. Whether you prefer to refer to their CVE number or their nicknames, these nasty vulnerabilities are showing up on security scans recently and causing concern for many different applications. What does that mean for BPPM?

 

BMC ProactiveNet Performance Manager is not affected by many of these vulnerabilities. BPPM has not been impacted as much as some application.  This chart will show which vulnerabilities require action.

 

 

Vulnerability

CVE number(s)

Remediation

Heart-bleed

CVE-2014-0160

OpenSSL 1.0. through 1.0.1f (inclusive) branches are vulnerable OpenSSL 1.0.1g is NOT vulnerable OpenSSL 1.0.0 branch is NOT vulnerable OpenSSL 0.9.8 branch is NOT vulnerable BPPM 9.0 runs with Open SSL 1.0.0e so it is NOT vulnerable. BPPM 9.5 runs with Open SSL 1.0.1c and so IS vulnerable.

 

The patches for BPPM 9.5 on all supported platforms are available on ftp://ftp.bmc.com/pub/BPPM/PATCHES/9.5/HeartBleed_Patch. Please see the file ‘readme_BPPM_OpenSSL_Heartbleed_fix_PS.txt’ for installation instructions.

Injection Bug

CVE-2014-0224

CVE-2014-0221

CVE-2014-0195

CVE-2014-0198

CVE-2010-5298

CVE-2014-3470

BPPM Server 9.5 should be using OpenSSL 1.0.1g if it was patched due to "Heartbleed" bug.  

This 1.0.1g does have the "CCS Injection" bug, but it was found that BPPM server is not vulnerable to this "CCS Injection" bug because of how it is being used. 

 

Both the client and server have to be running OpenSSL for the "CCS injection" exploit to work. Since all browsers (IE,chrome,firefox,safari) do not use OpenSSL,  the BPPM web console https sessions are not vulnerable.

Shellshock

CVE-2014-6271

CVE-2014-7169

The BPPM server does not use bash internally; it uses only c shell or shell scripts.  BPPM is not affected by the Shellshock bug.

Poodle

CVE_2014_3566

BPPM is impacted and users should disable Apache SSL V3.0 in BPPM for POODLE vulnerability

1. Stop BPPM Server with "pw system stop"

2. For BPPM 9.5 and 9.6 versions -->  <BPPM HOME>\pw\apache\conf\extra\httpd-ssl.conf (Windows)

 

<BPPM HOME>/pw/apache/conf/extra/httpd-ssl.conf (Linux/Solaris)

 

For BPPM 9.0 and 8.6 versions -->  <BPPM HOME>\pw\ApacheGroup\Apache\conf\httpd-ssl.conf (Windows)

<BPPM HOME>/pw/Apache/conf/httpd-ssl.conf (Linux/Solaris)

 

3. Make the following change in the platform specific file.

Add the following line in the httpd-ssl.conf file in the "SSL Cipher Suite" section:

SSLProtocol all -SSLv2 -SSLv3

4. Restart the ProactiveNet Server with "pw system start"

Ghost

CVE-2015-0235

As this flaw stems from the glibc function and manifests itself via the gethostbyname() function, we have not found it to be exploitable in any BMC products.

Freak

CVE-2015-0204

CVE-2015-0291

BPPM is not affected - BMC TrueSight Infrastructure Management (formerly BMC Proactivenet Performance Management Suite) 9.5 and 9.6 - ships with export ciphers disabled

 

Only BPPM versions 8.6 and 9.0 are affected by this vulnerability. To disable the EXPORT ciphers for version 8.6 or 9.0, please follow these steps:

 

   1. Stop BPPM server with 'pw sys stop' command.

 

   2. Backup the file <BPPM HOME>\pw\apache\conf\extra\httpd-ssl.conf (Windows) or <BPPM HOME>/pw/apache/conf/extra/httpd-ssl.conf (Linux/Solaris)

 

   3. Modify the httpd-ssl.conf file and add "!EXP" to the SSLCipherSuite setting.  Remove "+EXP" if it appears.

 

   4. Start BPPM server with 'pw sys start' command

LogJam

CVE-2015-4000

BPPM is not affected.

 

Didn't see a vulnerability on the list? Please open a ticket with Customer Support and provide the CVE number or security scan results and we will investigate it for you.  Please also check our Knowledge Base regularly as we do update it when we find new vulnerabilities which require modifications to the product. Usually searching by CVE number will help find a given vulnerability.

 

 

 

 

 

If you would prefer to upgrade OpenSSL and Apache for BPPM 9.5+, you can use the following instructions if running on Windows.

 

How to upgrade BPPM 9.5 to use OpenSSL version 1.0.1i and Apache version 2.4.10 (or better) on a Windows server

 

Below are the steps to manually upgrade BPPM 9.5 to Apache 2.4.10 with OpenSSL 1.0.1i on a Windows server:

 

Note 1: These steps are for Windows operating systems only

Note 2: Please perform these steps on a BPPM server in a test environment before performing them on the production environment

 

Prerequisites:

Please ensure that you have installed the Visual C++ 2010 SP1 Redistributable Package x64 : VC10 SP1 vcredist_x64.exe

 

Step 1) Download Apache 2.4.10 (VC 10 win 64-bit) from http://www.apachelounge.com/download/ and unzip the file to a known location.

 

Step 2) Stop the BPPM application

 

Step 3) Make a backup of the \ProactiveNet\pw\Apache directory or you can make a backup of the \ProactiveNet and sub-directories

 

Step 4) Replace the Apache folder from Step 1 with the \ProactiveNet\pw\Apache directory

 

Step 5) Copy the following files from Apache backup from Step 3 and paste them at the respective location below:

 

-pw\Apache\conf\httpd.conf

-pw\Apache\conf\extra\httpd-ssl.conf

-pw\Apache\conf\extra\httpd-proxy.conf

-pw\Apache\conf\my-server.cert

-pw\Apache\conf\my-server.key

-pw\Apache\conf\TunnelAgent

 

Step 6) Restart the BPPM application

 

We do not have a set of instructions to upgrade the version of Apache/OpenSSL on Solaris; the basic steps are comparable with the specific differences being the locations of the files, folders, subdirectories.

 

The ApacheGroup/Apache directory structure is only for Windows.  On your Unix system, the Apache installation is in the pw/apache subdirectory shown in your output.  That's where you can update these files.

There aren't any separate instructions written up for Solaris.  It would basically be the same, some slight differences:

 

In the conf dir, there are server.crt and server.key, not my-server.crt and my-server.key.

There is no agentPem.crt.

 

The modules directory has mod_jk.so, not mod_jk-1.2.28-httpd-2.2.3.so.

 

For the openssl download, it looks to be available from unixpackages.com (and the site indicates that it has the updated versions that take care of the vulnerability.

 

BMC definitely recommends upgrading to the latest version of BPPM rather than patching the Apache/Open SSL versions as the latest product version has been certified by QA and any change to that environment may lead to problems or performance issues. The rule of thumb should be to consider the upgrade of BPPM before considering an upgrade of Apache/OpenSSL.

 

For any questions about the security vulnerabilities or any other Apache/OpenSSL concerns, please contact Customer Support for further assistance.

 

 

 

 

 

Newly Published Knowledge Articles - New Content has been added over the last month!

 

This is our opportunity to share with you some of the most recently created knowledge articles in case they may help you with something you would like to know more about.

 

KA426693 - Error adding CMA global threshold to a "Unix and Linux - HP-UX and Linux" or "Unix and Linux - Solaris and AIX" solution

KA426707 - Installation of Service Resolution on BPPM completes with warnings if the username/password for Oracle instance has been changed from the default of proact/proact

KA426607 - The cmapolicymigration utility will still try to connect to HTTP port 80 even if BPPM has been reconfigured so that Apache webserver uses a custom port

KA426917 - The cell initialization is taking a long time and is preventing BPPM from starting up

KA426748 - How can I close all events of the same severity from a command line?

KA426600 - If the operations console is idle for a small period of time, a blank Navigation Pane Option Error popup message appears. 

KA426616 - Why are the Remote Agents not appearing under Device -> RemoteAgent in the Admin console?

 

Popular Knowledge Articles - Here are some of our most commonly used articles over the last month!

 

KA357339 - How to configure/scale ProactiveNet (MaxHeap, RAM, etc.) on server components like jserver, rate, Agent Controller and remote ProactiveNet Agent.

KA399915 - Events are not seen in 9.x BPPM Collectors after KB is reload or Cell is restarted.

KA417354 - How to upgrade BPPM 9.5 to use OpenSSL version 1.0.1i and Apache version 2.4.10 (or better) on a Windows server?

KA425524 - On the SNMP Adapter Configuration Manager, when you push the publish button nothing happens and there is no message written to the lower window in the configurator screen.

KA409289 -After installing BPPM 9.5, LDAP user is unable to login - "BMC-BSW000609E Failed to find user groups for user xxxxxx"

 

 

 

Looking for a previous blog posting? Find it here:  BMC TrueSight Pulse Blogs

 

 

Feedback Request:

Help us help you! Use the rating system at the bottom of this blog to rate this post! Feel free to comment as well.
What topics would you like to see?

Share This:

There seems to have been some interest in both SCCM and SCOM monitoring in BPPM lately. Most people who have an interest in this type of monitoring know all too well the differences between SCCM and SCOM and which one is preferred depending on the monitoring environment, but let’s a quick look at both and then see how we can monitor these tools in BPPM.

 

Microsoft's System Center Operations Manager (SCOM) is a monitoring tool to give administrators the ability to monitor the health of their environments. SCOM is used to monitor the health and performance of everything from servers to individual applications in Microsoft Windows environments.

 

Microsoft’s System Center Configuration Manger (SCCM) is Microsoft's all-in-one systems management assistant; a self-service solution a designed to evaluate, deploy and update servers and devices in a variety of environments. SCCM provides administrators with the capability to manage all aspects of Windows-based desktops, servers and devices from a single hub, giving them even more control over their IT infrastructures.

 

Once the IT team has their Windows management system in place, let BPPM monitor it for you!

 

Does BPPM have an out of the box way to monitor SCOM performance?

 

BMC ProactiveNet Performance Management 8.6 SP3 and later supports SCOM 2012 monitoring. For more information, please see our online documentation about third party products. In the Admin console, you will the see the adapter name as "SCOM 2007" but you can still integrate it with SCOM 2012.

 

The BMC SCOM Adapter can monitor the following SCOM versions:

 

- SCOM 2007

- SCOM 2007 SP1

- SCOM 2007 R2

- SCOM 2012

- SCOM 2012 SP1

- SCOM 2012 R2

 

NOTE: SCOM 2012 has removed the Root Management Server (RMS); the Root Management Server (RMS) Emulator must be installed for the BMC SCOM Adapter to monitor SCOM 2012.

 

 

BPPM 9.6 SCOM support

BPPM 9.5 SCOM support

 

In order to help you determine what you would like to monitor, we have the SCOM Adapter Monitor Types Reporter tool. The SCOM Adapter Monitor Types Reporter tool is an executable program that provides an XML report of all devices, monitor types, and relevant attributes available on the SCOM server in the BMC ProactiveNet environment.

 

You must have .NET 3.0 or later installed for the application to run.

The SCOM adapter monitor types reporter information can be used for the following:

 

 

•Determine which attributes are relevant to various devices. By using this information, determine which attributes must be selected on the BMC ProactiveNet Operations Console for a particular device.

•Verify whether the SCOM Rule is collecting data on the SCOM server.

 

For each monitor type, an XML will be generated with the relevant data on the current directory.

For monitor types that are not used for collection (there is no device for those), no XML will be generated.

 

 

Does BPPM integrate the SCOM events as well as performance data?

 

1) The BPPM SCOM Adapter is an adapter to bring in data not events.

2) To bring in SCOM events into BPPM there are 2 options:

2a) BMC offers a 3rd party partner add-on "Seamless Technologies Event Integration for BMC ProactiveNet Performance Management" that can be used to bring in events. This can be found under BPPM suite on the EPD download site under ->BMC Event and Impact Management - License Add-on ->BMC Performance Management - >Third Party and Custom Analytics License Add-on

2b) Users can create their own mechanism within SCOM to msend events into BPPM.

 

 

How can I troubleshoot SCOM data collection issues?

 

Setting up SCOM Adapter debug is recommended, that way, we can see the communication attempts.

Here are the steps to collect debug.

 

  1. On the BPPM agent machine, open the scom.conf file located in the <installDirectory>\pw\monitors\shared\scom directory.

  2. Comment out the line "pronet.scom.ntdebugging.enabled=true" as this line is no longer used by the adapter.

  3. Change the following variable to true: dll.Logger.debugEnabled=false. This is the variable which enables the native debug.

  4. Enable debug for the agent with command 'pw debug on -a <Agent Name>'.

  5. Perform discovery and note the exact time you did this operation.

  6. Collect the entire log directory BPPMAgent\Agent\pronto\logs and send to Support

 

What about SCCM is it monitored in BPPM?

There is no 'out of the box' solution for SCCM but there are several options for creating a custom solution, see below:

 

Users can create their own custom KM using the following resources

Building a PATROL Knowledge Module Developers Guide

Advanced PATROL Knowledge Module Development

Event Adapters user guide (for SNMP monitoring)

REST api integrations

Additional REST api's (9.6)

 

We would also encourage the use of the BMC Community as other members may have had experience setting up monitoring for SCCM and may be able to offer assistance.

 

So while we do offer the SCOM adapter, we do not have a similar adapter for SCCM performance monitoring out of the box. The majority of the requests we receive are for SCOM data, but if you have an interest in SCCM monitoring, I would urge you to submit an Idea in the BMC Community to request investigation regarding possible monitoring options.

 

BMC Ideas is a way to provide enhancement requests within our growing BMC Community. We are offering you the opportunity to submit on and vote for your requests for enhancement for your favorite BMC Products!  Check out these short video presentations detailing how to get started with BMC Ideas.

 

"    Introducing Ideation

"   Accessing Ideas

"    Interacting with Ideas

"    Submitting Ideas

 

 

Computer.png

 

Newly Published Knowledge Articles - New Content has been added over the last month!

This is our opportunity to share with you some of the most recently created knowledge articles in case they may help you with something you would like to know more about.

 

KA425524 - On the SNMP Adapter Configuration Manager, when you push the publish button nothing happens and there is no message written to the lower window in the configurator screen.

KA425441 - Is it possible to force propagation of events to the jserver?  

KA425739 - BPPM Self Monitor KM shows ImpactManager process down when it is really running

KA425616 - How are multiple enumerated values represented in the BPPM CMA policy import file.

KA425403 - Event propagated from other cells to BPPM, mquery shows the event in BPPM, but user console does not show the event.

KA425317 - In the operations console, the event details pane is slow to update when selecting an event.

KA425245 - PATROL for Unix 9.13 install failed on a HP-UX .11.31 U ia64 when using the "BPPM repository version 9.6.02 - Base March 2015" package

 

 

Popular Knowledge Articles

KA419548 - How to clean up the Marked for Delete (MFD) sooner than the 7 days default period in BPPM 9.5 and 9.6?

KA423528 - Beta for BMC TrueSight Operations Management 10.0: CMA is not getting launch. Customer was not able to open CMA in 3 browsers (Mozilla, Chrome, IE)

KA296013 - How to manually sync HA cells

KA399534 - How to allow members of a BPPM user group to see events from devices.

KA328581 - How can I clear all events and alarms from BMC ProactiveNet Performance Manager Server?

 

Looking for a previous blog posting? Find it here: BMC TrueSight Support Blogs

 

Feedback1.jpg

Feedback Request:

Help us determine how we are doing. Use the rating system at the bottom of this blog to rate this post! Feel free to comment as well. We want to hear from you!

Share This:

We have seen a rise in interest regarding custom Knowledge Modules (KM) and importing them into BMC ProacitveNet Performance Manager (BPPM). While we have touched on this topic before, we can expand it a bit more with a few more details and even a Best Practices Document for future reference. The questions does come up from time to time about how to import the custom KMs so let’s refresh our knowledge and/or learn something new depending on your comfort level with custom KMs.

 

First off, if you have not done so, please watch the BPPM Webinar recording done by BMC’s own Hutson Meeks where he discusses this topic for BPPM. Enabling Custom Knowledge Modules for BPPM 9.5 can be found here:  https://communities.bmc.com/docs/DOC-31482

This presentation is very similar to the details in this post but Hutson provides his expertise and tips.

 

High-level Process Workflow

It is recommend that you enable custom KMs for BPPM 9.5 in three major phases in the order listed below.

 

 

1)    Data Collection Enablement

2)    Policy Configuration Management Enablement

3)    Menu Command Enablement

 

 

You should completely test and validate the results of each phase before moving on to the next phase.

 

 

NOTE: If you choose to not enable Policy Configuration Management or Menu Commands the KM can still collect data into the BPPM 9.5 server and the KM configuration can be managed by agent configuration settings defined as rules in the Configuration Variables section of a monitoring policy.

 

 

Required Tools

The following tools are required to support the process of enabling, importing, testing and enabling PATROL Knowledge Modules for BMC ProactiveNet Performance Management 9.5.

 

 

1) BPPM 9.5 Server with CMA installed and operational

2) BPPM 9.5 Integration Service node installed and operational

3) BPPM 9.5 PATROL Agent installed and integrated with the BPPM 9.5 infrastructure

4) PATROL Classic Console version 3.6.00.1 (version 3.6.00 with the patch applied) or higher

5) PCIG Utility (Available with the PATROL common installer v9.6 under …\bmc_products\tools\pcig\ )

6) A common compression utility such as zip delivered with RHEL 6.4

 

 

All of these tools should be installed in a development environment.  Do not attempt to configure KMs for BPPM 9.5 in a production environment.

 

 

Enabling Data Collection Workflow Steps in Detail

The following steps provide details covering the entire process of enabling data collection with a custom KM for BPPM 9.5.  These steps should be completed in the order listed.  Attention to specific details should be observed, and recommendations should be followed.  Failure to follow these steps may result in unexpected or unintended results.

 

 

1) Validate that the custom Knowledge Module monitors and collects data in PATROL as designed and expected.  This is irrespective of BPPM.

2) Install and configure the tools listed under the Required Tools section above.

3) Deploy the custom Knowledge Module to be enabled to a test agent and the PATROL Classic Console using the latest version of the console.

4) Launch the PATROL Classic Console in Developer mode and load the custom Knowledge Module.  Load any dependent Knowledge Modules as well.

5) Configure the agent to operate in non-Policy mode and ensure the agent is not connected to a BPPM Integration Service node.

6) Add meta data settings to the Knowledge Module.

AppPropertiers160.pngParameterPropers2.png

 

 

7) Save the KM.

8) Commit the KM.

9) Validate that the Knowledge Module continues to monitor properly in PATROL.

10) Exit the PATROL Classic Console

11) Edit or create the KML file.  This file should contain a list all *.KM files to be loaded like it has been used in previous versions of PATROL.  Additionally, it is a best practice to add values for both the MetaKMLDisplayName and the MetaKMLDiscription in the KML file as shown in the example below.

!PATROLV3.2.0   FF08BBD43AC9210A8C6C41C85A315D3F

!++

!

! PATROL Session Knowledge Module

!

!--

! MetaKMLDisplayName = "Log Values"

! MetaKMLDescription = “KM that monitors numeric values from log file annotations”

KM_LIST = {

    "LOG_VALUES.km"

}

! 9999

12) Edit the Knowledge Module file adding release and revision information to the header of the KM file.  This should include the following information.

•    RELEASE number

•    REVISION number

•    PACKAGE value

•    DESCRIPTION

•    PRODUCTCODE

Example data from a KM file is shown highlighted below.

!PATROLV3.6.00.1i 3EC3A0E66408BF2FDB85D058CB4597BBE7EC56BBDB4BCA4A2D59D74EE5B65E7F

!#MSG_DOMAIN    km_sec

!++

!

! PATROL Session Knowledge Module

!

!—

!RELEASE    1.0.00

!REVISION    00

!PACKAGE    plv

!DESCRIPTION    PATROL Knowledge Module for Log Values

!PRODUCTCODE    plv

!PRAGMA allow: all

NOTE:  Both the PACKAGE value and the PRODUCTCODE should be a unique value specific to the custom KM.  Do not use BMC Software package values and/or product codes.  You can get a list of currently used values in your environment from the BPPM server where CMA is installed and used.  A list of these values is in the solution_list.xml and Solution_Mapping.xml files.  You can find these files in the following directory on the BPPM server where CMA is installed.

 

On UNIX/Linux: $BPPM_SERVER_HOME/pw/pproxy/depot_directory/bmc_products

On Windows:     %BPPM_SERVER_HOME%/pw/pproxy/depot_directory/bmc_products

Review the content of these files on your system if you are not certain.

 

NOTE:  If you do not enter the release and revision information into the KM file(s) the related application classes will not be processed in the BPPM server.  When the agent connects to the IS node the application classes without release and revision information will be rejected and an error event will be generated as shown below.

 

UnableToPRocess.png

13) Copy all the files related to the custom Knowledge Module to a backup directory.

a.    KML file

b.    KM files

c.    PSL files

d.    LIB files

e.    Etc.

14) Apply agent configuration rules to the agent so that the custom KML is in the KM preloaded list and the agent is configured to connect to the BPPM 9.5 test Integration Service node.

15) Stop the PATROL Agent.

16) Delete all the files related to the Knowledge Module from their respective PATROL Agent directories and the PATROL Classic Console cache.  You will be reinstalling them using a silent install package that you create in the BPPM 9.5 CMA Deployable Packages Repository.

17) Create a subdirectory for the custom Knowledge Module under the location where you have installed the PCIG utility. For example if you installed the PCIG utility in the directory shown below, create a directory for the custom Knowledge Module there as shown.  In this example the custom Knowledge Module is named LOGVALUES.

LinuxOutput4.png

 

18) Create respective sub-directories for all the Knowledge Module files under the location where you have installed the PCIG utility.   See example below.

Output4.png

 

 

 

19) Copy all the Knowledge Module files from the backup location to their respective directories under the directory you created for the custom Knowledge Module.  If you are providing a default configuration settings in a PATROL agent configuration “cfg” file (or a filename.current file) copy the file to the lib directory under the directory you created for the custom Knowledge Module with the same name.  See example shown below.

Output5.png

 

20) Run the PCIG utility from the directory it is installed in and source the Knowledge Module files from the subdirectory you created for the custom Knowledge Module.  Enter the same syntax as shown below for all command line arguments.  In this example, the Knowledge Module files are in their respective subdirectories under the LOGVALUES directory as noted above.

./pcig -p plv -r 1.0.00 -s LOGVALUES/ -l ALL -t LogValues

The following table lists the command line arguments with the example values from the command above.  (This was run on Linux.Windows follows the same format.)

Table6.png

Argument    Purpose    Example    Comments

-p    product    plv    Enter a value that does not match or conflict with any other products.

-r    release number    1.0.00    Enter a 3 segment value.  Do not enter only one or two segments.  (For example 1 and 1.0 would not work.)

-s    location of all source files and their respective sub directories    LOGVALUES/    This is the top level directory under which custom KM files are stored.  The subdirectories must follow the same structure as a normal PATROL Agent and KM install.  This directory should be a subdirectory in the directory where you are running PCIG. Use this syntax exactly with the proper subdirectory name followed by a forward slash at the end.  The following is an example.  Suppose you are running the PCIG utility in /home/patrol to create a package for the “Log Values” custom KM.  The directory structure for the tag you are creating a package for would look like this:

 

/home/patrol/LOGVALUES

/home/patrol/LOGVALUES/lib

/home/patrol/LOGVALUES/lib/psl

/home/patrol/LOGVALUES/lib/knowledge

 

-l    comma separated list of supported OS types    ALL    Make sure this matches the Knowledge Module design

-t    product title name    LogValues    This is the name of the compressed ZIP file that is generated to be imported.

 

 

 

Note: Command line argument information can be displayed at a command prompt by running the PCIG utility with no arguments as shown.

[root@BPPMRHEL62-HM LINUX-X64-64]# ./pcig

PATROL Common Install generator v9.5.00 (build:20140921815)

Usage: pcig.exe -p product -r release -s source_path [-l os_list] [-t title] [-c]

-p <product>:  Required name (also specifies name of output ppf file without ".ppf")

-s <source_path>: Required path to package member files.  The files under <source_path> are copied to <dest_path>/products/<product_name> and gzipped, and their respective entries are added under the files section of the ppf.  The ppf and cat file are placed in  <dest_path>/Products/<product_name>, and a copy of the ppf is also placed in <dest_path>/Index/.

-r <release>: the version (vv.mm.rr) of the package to be used with BPPM in the format of.

-l <os_list>: comma separated list of OS types (possible values: AIX,SOLARIS,HP-UX,LINUX,WINDOWS,ALL,ALL-UNIX).

-t <title>: Product name, to be used on the BPPM CMA repository UI

 

The PCIG utility will create a bmc_products directory and a ZIP file for the solution.   Below is an example output when running the PCIG utility.

Output7.png

 

NOTE:  At the time this documentation was created the compressed ZIP file generated by the PCIG utility was not importable to the CMA Monitoring Repository.  To resolve this you should recursively compress the bmc_products directory that is created by the PCIG utility and import the ZIP file generated

21) Compress the bmc_products directory that was created by the PCIG utility into a ZIP file.  Do not attempt to use the folder compression capability that is built into Microsoft Windows.  Use a commonly used compression utility such as the zip command on Linux or 7-Zip on Windows.

Output8.png

 

22) Import the Zip file you created into the BPPM 9.5 CMA Monitoring Repository.  Import as a single solution.

Output9.png

 

23) Create a silent install package in the BPPM 9.5 CMA Deployable Package Repository.  Provide a unique and meaningful name for the package following configuration best practices.  Do not include the agent or any other KMs in the package.

 

Output10.png

 

24) Download the silent install package that you created for the Knowledge Module from the BPPM 9.5 CMA Deployable Package Repository and move it to the test managed node.

25) Run the silent installer for the package

26) Start the PATROL Agent.

27) Verify that the Knowledge Module application class(es) appear(s) as monitor type(s) in the BPPM server operations UI

Output11.png

 

28) Validate that data is being collected as expected.

 

Output12.png

 

Enabling Policy Configuration

Enabling policies for the KM configuration requires entering XML data into the Input tab of the properties for the KM container.  The screen shot below shows an example of the Input tab.

Output13.png

 

Practice and leveraging examples will help you learn what data is needed.  Note the following points.

 

 

1) Much of the structure and content of the XML data is the same for various KMs.  This includes the host configuration sections and various labels.  This means you can easily copy existing Input XML data and edit it to create the XML data for your custom KM.

2) XML data that is unique to your KM is mainly titles and content in the attribute sets that define the specific configuration settings for your custom KM.

3) The XML Input data is saved into the KM XML file.  It is not saved in a separate file to be managed with the PCIG utility.

This illustrates an example of Input XML data.  Only the data highlighted in blue text was edited from a copy, and an additional attribute was added.

 

NOTE: Notice the ID values in red text.  These values correspond to PATROL agent configuration variables.  When the policy is applied, PATROL Agent configuration variables that contain the ID values are created under the /ConfigData/<KM name> branch.  An example of the /ConfigData/<KM name> data is shown after the XML example.

 

 

<KMConfigurationMetadata>

<KMLevelConfiguration dataModelMajorVersion="1" dataModelMinorVersion="1">

</KMLevelConfiguration>

<ConfigurationParameters>

<ConfigurationParameter>

<List description="List of remote hosts" id="HOSTS" indexedBy="host" isMandatory="true" label="Host Log Values Configuration">

<AttributeSet description="Enter Host Name for which the specified configuration applies" i18nIdForDescription="4" i18nIdForLabel="3"  id="HostConfiguration" label="Host Details">

<Attribute>

<String default="localhost" description="Enter the Host Name" i18nIdForDescription="6" i18nIdForLabel="5" id="host" isMandatory="true" label="Host Name">

</String>

</Attribute>

<Attribute>

<AttributeSet id="LogValues" label="Log Values Configuration Options">

<Attribute>

<String default="" description="Enter the log instance to monitoring." id="LVInstance" isMandatory="false" label="Log Instance">

</String>

</Attribute>

<Attribute>

<String default="" description="Enter the alarm search string value." id="LVSearchString" isMandatory="false" label="Search String">

</String>

</Attribute>

<Attribute>

<String default="" description="Enter the data delimiter." id="LVDelimiter" isMandatory="false" label="Delimeter">

</String>

</Attribute>                 

</AttributeSet>

</Attribute>

</AttributeSet>

</List>

</ConfigurationParameter>

</ConfigurationParameters>

</KMConfigurationMetadata>

 

 

The PATROL configuration variables below illustrate content corresponding to the Input XML data above.

 

 

PATROL_CONFIG

"/ConfigData/LOG_VALUES/HOSTS/localhost/host" = { REPLACE = "localhost" },

"/ConfigData/LOG_VALUES/HOSTS/localhost/LVDemiliter" = { REPLACE = "2" },

"/ConfigData/LOG_VALUES/HOSTS/localhost/LVInstance" = { REPLACE = "MyTestLogPN0" },

"/ConfigData/LOG_VALUES/HOSTS/localhost/LVSearchString" = { REPLACE = "sessions" }

 

 

The policy configuration screen below illustrates the result of the Input XML data after it is imported as part of the KM into the CMA repository.

Output14.png

After you have entered the XML data, save the KM and work through the same packaging and import process using PCIG that you followed to enable the KM for data collection.  Test the policy configuration before moving on to enabling Menu commands.

NOTE:  Most KMs will need to be edited where the pconfig PSL command is used to interact with the agent pconfig database so that it leverages the PATROL agent configuration variables under the /ConfigData/<KM name> branch.  It is generally easier to configure the agent to collect data into the BPPM server in non-policy mode first, then apply the policy and finally edit the KM based on the agent configuration variables applied by the policy.

 

 

Enabling Menu Commands in the BPPM UI

The following steps illustrate how to enable Menu Commands in the BPPM UI.

 

 

1) Open the properties for the Menu Command and go to the Command tab.

2) Copy the command text and save it in a backup text file.

3) Click on the General tab and select Generate Auto ID as shown below.  Do not select the Annotate choice if the menu command prompts for user input. (Annotate can be used to automate the command.)

Output15.png

 

Click Yes to continue.  The command text can be copied from the backup file and pasted into the Command tab if it is lost.

4) After clicking Yes notice the Command ID is generated as shown in the example below.

 

Output65.png

5) The menu command function is saved as a file in the PATROL Console Cache PSL directory as shown in the example below.

 

Output17.png

6) Include the Menu Command ID <name>.lib file in the PSL source directory for PCIG.

7) Work through the same packaging and import process using PCIG that you followed to enable the KM for data collection and Policy configuration management.

8) Verify the Menu Command was created in the BPPM UI

Output18.png

General Recommendations

Do not use the Microsoft Windows compressed folders capability to compress the package.  Use a compression utility like 7-Zip.

 

Do not attempt to combine multiple KM solutions into one package.  Create separate packages for each.


Monitoring in BPPM will not function for Knowledge Modules which are not XML compliant and that are loaded on a 9.5 agent.

 

PSL code should be stored in PSL files using the "Save to file" option in the developer console while developing Knowledge Module.
This should be done instead of storing the code in the Knowledge Module files.  This will reduce the size of the XML file.

 

Keep in mind the XML file for the Knowledge Module is generated by the PATROL console and saved into the PATROL Console cache.

 

Start with a working Knowledge Module in PATROL.

 

Do not try to mix Knowledge Module development for monitoring and development/editing for BPPM 9.5 compatibility.  Work in a logical order.

 

Observe and follow general Knowledge Module development best practices.

 

Observe and follow general software development best practices.

 

Keep your code organized and follow the recommended process.  Do not jump ahead.  Do not skip steps.


Establish, document, and follow a version-revision numbering methodology.


Do not work though the enablement process in production.  Complete Knowledge Module enablement for BPPM 9.5 in a development and test environment before you import the final Knowledge Module solution package into production.

 

Do not use product names that match or conflict with other product names including BMC product names.


Do not use Knowledge Module names that match or conflict with other Knowledge Module names including BMC provided names.


Do not use package or solution names that match or conflict with other package or solution names including BMC provided names.


Maintain release and revision numbers properly.  This is especially important if you plan to have multiple release and/or revision numbers in use over time.

 

Use different names for the solution package created by the PCIG utility and the silent install package you create in the BPPM 9.5 CMA Deployable Package Repository.  This will help you keep track of the two files separately and not get them mixed up.  For example:

  1.   Name the file created by the PCIG utility based on the product name (Ex. plv.zip – “plv” is short for the custom KM solution named “Patrol Log Values”).
  2.   Name the deploy-able package according to the Knowledge Module name (Ex. LogValues.zip).

Be careful with text editors.  Do not use Microsoft WordPad or Microsoft Word for editing and saving files.  Use vi on Linux and UNIX.
Use Notepad or a programmer’s text editing utility like Notepad++ on Windows.  This will prevent the introduction of special characters that will cause issues.

 

Do not manually edit files except where recommended and required.


Start with a simple KM and learn the process before moving on to a more complicated KM.

 

It is a best practice to implement a container for each custom KM application class, especially if you expect multiple instances to be monitored.  This will improve UI navigation in BPPM so that all like instances are grouped into a container.

 

Make a backup of all KM related files before you begin editing.


Work in stages and take backups of each stage before moving on to the next stage.  For example get data collection working first, then move on to policy enablement, and finally enable menu commands.

 

Do not install or use other tools in the development environment that may interfere with the development process.  Examples include older PATROL Console versions, older BPPM infrastructure components that may be integrated with the test agent(s), PATROL Central, etc.

 

This entire Best Practices Document is available for download from our Knowledge Base under knowledge article KA400714

For more details about building and packaging custom see our online help: Building and packaging custom KMs.

For information about building a KM, see Building a PATROL Knowledge Module Developers Guide

Computer.png

 

 

Newly Published Knowledge Articles - New Content has been added over the last month!

This is our opportunity to share with you some of the most recently created knowledge articles in case they may help you with something you would like to know more about.

 

KA424135 - Cell loop and running 100% CPU while processing MC_SM_IMPACTS_REPORT event and deleting MC_SM_IMPACTS data instances.

KA424020 - BMC PATROL for Web URL Monitoring KM, after configuring an URL for monitoring, getting error 'handshake failure'.

KA424017 -  Is BPPM affected by the OpenSSL vulnerabilities CVE-2015-0204 and CVE-2015-0291?

KA422603 - Where is the send_trap utility in Windows?

KA423763 - What can we use instead of Tunnel proxy and TCP proxy in BPPM version 9.5 and higher?

KA422471 - Promotion from Impact Model Designer (IMD) is failing with the errors 'Publication for job ID null has failed'. and 'Promotion of Sandbox Changes has Failed. - Failed while doing promotion.' 

KA422559 - Tips for Email2Event problems

 

Popular Knowledge Articles

This list represents our most widely used knowledge articles, take a look to see if they may help you too!

 

KA403892 - Troubleshooting Guidelines for BPPM with Oracle Database

KA356644 - ProactiveNet Agent error - "java.lang.OutOfMemoryError: Java heap space"

KA287306 - How to Delete ProactiveNet Auto Sync Monitor Instances and devices from the system with respect to BMC Patrol Adapters?

KA316131 - What are the different ways of enabling cell trace?

KA352032 - Diagnosing problems with ProactiveNet PATROL Adapter without Service Integration

 

Looking for a previous blog posting? Find it here: BMC TrueSight Support BlogsBMC TrueSight Pulse Blogs

 

Feedback1.jpg

 

Feedback Request:

Help us determine how we are doing. Use the rating system at the bottom of this blog to rate this post! Feel free to comment as well. We want to hear from you!

Share This:

Users who are upgrading to BPPM 9.6, please be advised of an important perquisite for upgrading to BPPM 9.6. BMC Software is alerting users to perform the following steps before upgrading to BMC ProactiveNet 9.5.00 on Microsoft Windows computers. This requirement is applicable to 9.6 as well.

 

Before upgrading:

 

1. Take a backup of the computer in which the BMC ProactiveNet Server is installed.

2. Update the following files (if available) located in the <installationDirectory>\pw\custom\conf directory:•For the JServer process, comment the following line in the pnjserver.conf file:

 

ProcessName=$PROACTIVEHOME\jre64\bin\java_jsrv.exe

•For the Rate process, comment the following line in the pnrate.conf file:

 

ProcessName=$PROACTIVEHOME\jre64\bin\java_rate.exe

•For the Agent Controller process, comment the following line in the pnagentcntl.conf file:

 

ProcessName=$PROACTIVEHOME\jre64\bin\java_cntl.exe

 

•For the Agent process, comment the following line in the pnagent.conf file:

 

ProcessName=$PROACTIVEHOME\jre64\bin\java_agent.exe

 

This requirement is documented under:Alerting users to follow the key upgrade prerequisite on Windows - BMC ProactiveNet 9.6 - BMC Documentation

 

There is a problem where the files in pw\custom\conf contain “jre64” in the path and the path is now referenced as “jre”. This is evidenced by jre64 references in the proservices.log file see below:

JRE64.jpg

 

 

If you see this reference in your BPPM 9.6 ProServices.log file (\\BMC Software\ProactiveNet\pw\pronto\logs) your upgrade did not go well. This can have a negative impact on your environment. The only way we can fix this problem completely is to restore from backup and do the upgrade again after modifying the custom configuration files before the upgrade.

 

Any attempts to modify the files after the fact will result in an unsupported environment. We cannot guarantee there will not be any other negative effects of the missed change before the upgrade. Our experience with other customers who have attempted to modify the files after the upgrade resulted in several different product issues which all traced back to a botched upgrade.

 

Therefore, we require you to restore from backup and start the upgrade process again.  We have seen this issue with the upgrade between 9.0 and 9.6 but it may affect other versions as well. So please be sure to include the changes above in your perquisites for upgrading to BPPM 9.6.

 

 

In order to be sure you are on the right track for your upgrade, we encourage you to take advantage of our free AMIGO program. There is a BPPM 9.6 Checklist for AMIGO which contains the details of the requirements for the upgrade. This checklist does contain a check for the jre64 indicator in the conf files.

 

 

Check each of the conf files in the pw\custom\conf directory for the parameter:   ProcessName=$PROACTIVEHOME\jre64\bin\.......

Just before starting the upgrade, comment out the ProcessName line:

  #ProcessName=$PROACTIVEHOME\jre64\bin\......

Do not restart BPPM after making this change before the upgrade is run.

 

 

The BPPM Assisting MIGration Operations (AMIGO) program is designed specifically to help you upgrade quickly, easily and safely.

 

 

The AMIGO program includes:

» A “Question and Answer” session before you upgrade

» A review of your upgrade plan with Customer Support

» An upgrade checklist

» Helpful tips and tricks for upgrade success from previous customer upgrades

» A follow-up session with Customer Support to let them know how it went. This will help BMC to enhance the process.


To get started review the checklist items found here: KA408618

Then open a BMC Support issue containing your environment information (product, version, OS, etc.) and the planned date of the installation, if known. We will contact you promptly, and work with you to ensure a successful and timely outcome.

 

Computer.png

 

 

Newly Published Knowledge Articles - New Content has been added over the last month!

This is our opportunity to share with you some of the most recently created knowledge articles in case they may help you with something you would like to know more about.

KA418568 How does BPPM 9.5 IBRSD look up the BPPM server, and cellname to send INCIDENT_INFO events to? 

KA407196 Is there a way to migrate thresholds from one BPPM server to another?

KA380112 How the TAG match works between CMA on the BPPM side and the PATROL Agent side

KA386298 The Diagnostics menu option is grayed out when right clicking on an event within the ProactiveNet Operations Console

KA400040 Details of shadow logging feature

KA405755 After manually closing an ALARM event with IX or mquery or msetmsg, the event is closed on BPPM but another new event is seen when threshold for that attribute is still in breached state.

KA359014 Need to automate the import of an enrichment file every 15 minutes   

 

Popular Knowledge Articles
This list represents our most widely used knowledge articles, take a look to see if they may help you too!

KA318711 How to change the hostname/IP Address of BPPM ProactiveNet Server on Windows Platform

KA330178 What ports are required on the firewall for the BMC PATROL Adapter within ProactiveNet Server 8.5 or 8.6?

KA361627 The installation of the ProactiveNet CMDB Extensions from BPPM 8.6.02 and 8.6.02.01 failed on Atrium (AR) version 7.6.04 SP2

KA357339 How to configure/scale ProactiveNet (MaxHeap, RAM, etc.) on server components like jserver, rate, Agent Controller and remote ProactiveNet Agent.

KA359011 How to configure/troubleshoot LDAP authentication in BPPM.

 

Looking for a previous blog posting? Find it here:  BMC ProactiveNet Pulse Blogs

Feedback1.jpg

 

Feedback Request:

Help us determine how we are doing. Use the rating system at the bottom of this blog to rate this post! Feel free to comment as well. We want to hear from you!

Share This:

When considering your upgrade to BPPM 9.6 we wanted to share an issue that has been detected by a few customers. The majority of our users, who have upgraded, have not encountered any issues. However, we did find an issue specific to non “Super Admin” accounts after the upgrade from BPPM 9.5 to 9.6. We have seen this issue where Event collectors, Devices, and Groups are not visible under Global directory for non “Super Admin” accounts.

 

All roles except "Super Admin” cannot view global groups in the Operations Console. e.g. read-only, data collection operator, service operator, cannot view global groups in the Main accordion within the Operations Console.

 

 

Here's an example of how to reproduce the issue in BPPM:

 

1) Create Role “NEWROLE” with all privileges except Super Admin.

 

 

RolesandPerms1.png

RolesandPerms2.png

RolesandPerms3.png

RolesandPerms4.png

RolesandPerms5.png

RolesandPerms6.png

RolesandPerms7.png

RolesandPerms8.png

RolesandPerms9.png

RolesandPerms10.png

RolesandPerms11.png

RolesandPerms12.png

RolesandPerms13.png

RolesandPerms14.png

     Then see the difference in the views in the Operations Console:

     User :

RolesandPerms15.png

Newuser:

RolesandPerms16.png

User:

 

Super Admin:

 

There is an open defect for this issue, defect QM001869140 and it will be addressed in a future release. For now, we do have a workaround to address the issue.

 

Please follow these steps:

1) Edit .\pw\pronto\pronet.conf

2) Change:

pronet.system.installationtype=upgrade

To:

pronet.system.installationtype=newinstall

3) pw system start

 

For access to the Knowledge Article with the same details as the workaround above, please visit: https://kb.bmc.com/infocenter/index?page=content&id=KA420718

 

Please do not allow this to keep you from upgrading. We recommend that everyone starts to plan their upgrade to BPPM 9.6. If you need assistance, please do not hesitate to take advantage of the free AMIGO program!

The BPPM Assisting MIGration Operations (AMIGO) program is designed specifically to help you upgrade quickly, easily and safely.

 

 

The AMIGO program includes:

» A “Question and Answer” session before you upgrade

» A review of your upgrade plan with Customer Support

» An upgrade checklist

» Helpful tips and tricks for upgrade success from previous customer upgrades

» A follow-up session with Customer Support to let them know how it went. This will help BMC to enhance the process.

To get started review the checklist items found here: https://kb.bmc.com/infocenter/index?page=content&id=KA408618

 

Then open a BMC Support issue containing your environment information (product, version, OS, etc.) and the planned date of the installation, if known. We will contact you promptly, and work with you to ensure a successful and timely outcome.

 

 

 

Newly Published Knowledge Articles - New Content has been added over the last month!

KA413229 - The installation of BPPM CMDB extensions fails with "Bad version number in .class file"

KA411122 - BPPM 9.5 and PATROL compatibility

KA407152 - When attempting to login to BPPM via LDAP, there is a long delay in the actual authentication.

KA400687 - "HTTP/1.1 415 Unsupported Media Type" error returned when trying to authenticate with BPPM Webservices using the REST API.

KA368895 - Can the BPPM Sybase database be moved to another machine for testing/rebuilding?

KA347707 - TM ART Adapter in Proactivenet BPPM error: "verify your username and password are correct" ANSWER: Make password have no special characters.

KA348997 - Perform a test to verify iBRSD integration is working

 

Popular Knowledge Articles

KA359827 - Which firewall ports and direction need to be open for an Atrium CMDB - BPPM integration?

KA356599 - After a promote/publish, I am unable to see the service model in the BPPM Admin/User Console.

KA396805 - Unable to delete device in BPPM Admin console

KA352299 - BPPM database tables & view and Schema information for integration with BSM Dashboards. 

KA359493 - Secondary HA cell unresponsive and running high CPU

 

Feedback1.jpg

 

 

 

Feedback Request:

Use the rating system at the bottom of this blog to rate this post! Feel free to comment as well. We want to hear from you!

Share This:

Now, there is a new way to watch Connect with BPPM Webinars, via iTunes Podcasts.

 

To get started click Connect with - TrueSight Infrastructure Management (BPPM) Series to subscribe to the podcast. 

Once you have subscribed they will automatically be synced based on your subscription options as the webinar videos are posted.

All previously recorded webinars are also available

 

Please let us know if you have any issues with accessing the webinar series. All feedback is welcome.

Share This:

It has been asked, whether BPPM 9.6 has the ability to collect and send out details regarding data gaps or data inconsistencies as is the case with previous versions of BPPM.

 

The answer is : Yes, we do have the ability to generate a data consistency report. While the need to rely on these reports has dramatically decreased with the release of BPPM 9.6, they are still produced and can be easily turned on or off with configuration settings. Data gaps are fewer and far between and if they do appear, this report can help identify the area of concern.

 

Here’s some basic information on the Data Collection and Consistency Status Problem report in BPPM 9.6:

We still produce a “Data Consistency” report and email it to the Admin email address, it just has a different layout than in previous versions.

 

DataCollectionReport.jpg

 

The Data Collection and Consistency Status Problem report is a consolidated report of both Data Gap and Data Collection. You can get the Data collection Status reports with URL at http://<bppm_server>/snapshots.

StatusReport.jpg

 

This report is sent to the email address of the recipients listed in the pw/etc/hosts/admin_user file. By default, report generation is enabled and gets generated every 720 minutes (12 hours).  You can turn off the report generation by modifying the pronet.rate.datagapcheck.enable property of the pw\pronto\conf\pronet.conf file, such that:
pronet.rate.datagapcheck.enable=0

Enabled.jpg

 

 

You can also modify the time interval of the report by updating the value of the pronet.rate.collcheck.checkinterval property in thepw\pronto\conf\pronet.conf file. The minimum time you can set for the report getting generated is 120 minutes.

PronetConf.jpg

Note

•The first report is generated at the time interval of 1440 minutes (24 hours) and the configuration time is doubled after every restart of the BMC ProactiveNet Server.

•Data Gap is not applicable for streaming instances

 

To get a detailed output of the report by email, set the following property value of the pw\pronto\conf\pronet.conf file to 1:

pronet.rate.collcheck.senddetailedoutput=1

The default value is zero.

EmailOutput.jpg

 

For information about changing email settings in Data Collection & Consistency Status Problem Report, see Configuring e-mail settings to receive alerts. You can also run the pw test mail command to see the email configuration for emailing these reports.


Have you seen data collection issues and inconsistent status problems with previous versions? If so, we encourage you to upgrade to 9.6 in the new year. Still have concerns about the upgrade? Let us help you. The BPPM Assisting MIGration Operations (AMIGO) program is designed specifically to help you upgrade quickly, easily and safely.

 

The AMIGO program includes:

» A “Question and Answer” session before you upgrade

» A review of your upgrade plan with Customer Support

» An upgrade checklist

» Helpful tips and tricks for upgrade success from previous customer upgrades

» A follow-up session with Customer Support to let them know how it went. This will help BMC to enhance the process.

 

 

To get started review the checklist items found here: https://kb.bmc.com/infocenter/index?page=content&id=KA408618

 

Then open a BMC Support issue containing your environment information (product, version, OS, etc.) and the planned date of the installation, if known. We will contact you promptly, and work with you to ensure a successful and timely outcome.

 

 

Newly Published Knowledge Articles - New Content has been added over the last month!

KA419884 - Is there any reduction to the size of the mcdb file or cell memory if a slot has a default value?

KA419883 - Is there an option to create a report or run a query to find the list of KPI that are enabled or disabled within BPPM 9.5?

KA419915 - The Admin cell remains greyed out under the Other Cells accordion in BPPM User Console.

KA419921 - The IBRSD plugin is failing to load and an exception is seen in the arjavaplugin.log

KA419989 - Since installing 9.5 SP1, when viewing DDA in the Admin console, why do they all have mc_bad_slot_names and mc_bad_slot_values slots with no value?

KA420005 - Are BPPM core components supported on Hyper-V servers?

 

Popular Knowledge Articles

KA359107 - Is it possible to migrate BPPM from the embedded Sybase database to an Oracle database?

KA321519 - Network Ports used with and for ProactiveNet 

KA347740 - BPPM Cell crashes when xact files grows rapidly

KA362420 - IBRSD services keeps intermittently crashing

KA347978 - How can I ensure that a BPPM PATROL adapter has automatic workflow disabled?

 

Looking for a previous blog posting? Find it here:BMC TrueSight Support Blogs

 

Feedback1.jpg

Feedback Request:

Help us determine how we are doing. Use the rating system at the bottom of this blog to rate this post! Feel free to comment as well. We want to hear from you!

Share This:

The POODLE vulnerability has been gaining attention throughout our field. The SSL 3.0 “POODLE” Security Vulnerability -- CVE-2014-3566 has affected several BMC products and does impact BPPM.

 

POODLE stands for Padding Oracle On Downgraded Legacy Encryption. This vulnerability allows a man-in-the-middle attacker to decrypt ciphertext using a padding oracle side-channel attack. More details are available in the upstream OpenSSL advisory.

 

POODLE affects older standards of encryption, specifically Secure Socket Layer (SSL) version 3. It does not affect the newer encryption mechanism known as Transport Layer Security (TLS).

 

The SSL protocol 3.0, as used in OpenSSL through 1.0.1i and other products, uses nondeterministic CBC padding, which makes it easier for man-in-the-middle attackers to obtain cleartext data via a padding-oracle attack, aka the "POODLE" issue.

 

Impacted BPPM versions:

BMC ProactiveNet Performance Management Suite 9.6

BMC ProactiveNet Performance Management Suite Server 9.5

BMC ProactiveNet Performance Management Suite Server 9.0

BMC ProactiveNet Performance Management Suite Server 8.6

 

For additional products affected, please visit BMC Product Information on POODLE vulnerability

BMC is providing a workaround for the security vulnerability of POODLE on BPPM Server systems.  BPPM does not utilize the feature that is vulnerable but Apache is installed as part of the installation.

It should be noted that if you upgrade your release version you will need to reapply this workaround as the same Apache .conf file will be overwritten.

1. Stop BPPM Server with "pw system stop"

2. Please backup the following files

For BPPM 9.5 and 9.6 versions -->  <BPPM HOME>\pw\apache\conf\extra\httpd-ssl.conf (Windows)

                                                          <BPPM HOME>/pw/apache/conf/extra/httpd-ssl.conf (Linux/Solaris)

For BPPM 9.0 and 8.6 versions -->  <BPPM HOME>\pw\ApacheGroup\Apache\conf\httpd-ssl.conf (Windows)

                                                         <BPPM HOME>/pw/Apache/conf/httpd-ssl.conf (Linux/Solaris)

                                                         <BPPM HOME>/pw/Apache/conf/httpd-ssl.conf (Linux/Solaris)

3. Make the following change in the platform specific file and save the file

Add the following line in the httpd-ssl.conf file in the "SSL Cipher Suite" section:

SSLProtocol all -SSLv2 -SSLv3

4. Restart the ProactiveNet Server with "pw system start"

 

SSLCipherSuite.jpg

 

 

That's it, once the change is made and saved, there should no longer be an issue with the Poodle vulnerability. If you have any questions or need additional information, please contact Support. This information is also referenced in our Knowledge Base under How to disable Apache SSL V3.0 in BPPM for POODLE vulnerability

 

 

Newly Published Knowledge Articles - New Content has been added over the last month!

KA418064 - What is the effect of applying multiple policies to the same PATROL agent in CMA?

KA418086 - What is the best practice to send events from the PATROL Agent to the BPPM server version 9.5?

KA418281 - When a CI is published how is the ComponentAliases slot value constructed?

KA418365 - If an Integration Service is stopped, I do not see a self-monitoring event (class PPM_SM_EV) to indicate it has been disconnected.

KA418886 - BPPM 9.5 - Events are shown with incorrect time since the Daylight Savings Time (DST) change.

KA419068 - After upgrading to BPPM 9.5 SP1, all event operations (Take Ownership, Assign To, Acknowledge Event, Close Event etc.) are greyed out.

KA419189 - Is it possible to change the value of mc_parameter_value slot for PATROL events to not contain so many decimal places?

 

 

Popular Knowledge Articles

KA382011 - I am unable to send events directly from Patrol Agent v9 to cell

KA352299 - BPPM database tables & view and Schema information for integration with BSM Dashboards.

KA324702 - How to Setup External Authentication in BMC ProactiveNet Performance Management (BPPM) 8.0.00 and above?

KA309641 - ProactiveNet jserver and rate processes are not starting. 

KA351085 -Connectivity issue between Patrol Agents and Integration Service

 

Feedback1.jpg

 

 

 

 

Feedback Request:

Are these blogs helpful to you? We want to hear from you. Let us know what you think or what topics you would like presented in our blog.

Share This:

Users are integrating PATROL with BPPM, but the big question seems to be what to do with custom KMs.

 

The best reference is our Webinar on Custom KMs and BPPM - If you missed the Webinar, you can view the details here BMC ProactiveNet Performance Management (BPPM) 9.5 Best Practices Webinar Series

 

The details are also available in our online help documents

For information about building a KM, see Building a PATROL Knowledge Module Developers Guide.

Before you begin

Here’s an overview of the workflow for setting up custom KMs in BPPM

Enable custom KMs for BPPM 9.5 in three major phases in the order listed

Data Collection Enablement

Policy Configuration Management Enablement

Menu Command Enablement

  

Test and validate results of each phase before moving on to the next phase

Optional or Phased Enablement

If not enabling, Policy Configuration Management Leverage rules in the Configuration Variables section of a monitoring policy or leverage PATROL & PCM

 

The KM can still collect data into the BPPM 9.5 server

General recommendation is to enable all that is necessary & possible

 

Required tools

BPPM 9.5 Server with CMA installed and operational

BPPM 9.5 Integration Service node installed and operational

PATROL Classic Console version 3.6.00.1or higher

BPPM 9.5 PATROL Agent installed and integrated with the BPPM 9.5 infrastructure

PATROL Common Installer Generator Utility (PCIG)

A common compression utility such as zip delivered with RHEL 6.4

Configure and setup all tools as you normally would.

 

NOTE:

All of these tools should be installed in a development environment.

Do not attempt to configure KMs for BPPM 9.5 in a production environment

Do not install or use other tools in the development environment that may interfere with the development process.

 

  • Older PATROL Classic Console versions
  • Older BPPM infrastructure components
  • PATROL Central Consoles

 

You can find the PCIG tool installer in the installation utility\bmc_products\tools\pcig directory of the BMC Installation Utility installer, version 9.6.

You can also go to  ftp://ftp.bmc.com/bmc/bppm/repo  and review the docx file.

 

To start using the PCIG tool for creating a BAP image for custom KMs, perform the following steps:

1. Copy the downloaded file and the product (KM) in a temporary folder.

For more information, see Downloading the product.

 

2. Extract the installation utility folder and the custom KM folder for which you want to create the BAP image.

The executable files, pcig-32.exe or pcig.l22 (for 32-bit Microsoft Windows or Linux), and pcig-64.exe or pcig.l64 (for 64-bit Microsoft Windows or Linux) of the PCIG tool will be located in the following directory, depending on the operating system:

 

•(Microsoft Windows): installation utility\bmc_products\tools\pcig

•(Linux): installation utility/bmc_products/tools/pcig

 

Before you can load a custom Knowledge Module (KM) in the BMC ProactiveNet Performance Management environment and configure it through BMC ProactiveNet Central Monitoring Administration, you must build and package the KM.

 

The PCIG tool builds and packages custom KMs and creates Product Package Files (PPFs), which are required for the build and package (BAP) image. The PCIG tool is supported only in Linux and Windows platforms.

 

 

Creating a BAP image for custom KMs

 

You can create a BAP image for custom KMs by running the following command:

$. /pcig<32-bit or 64-bit> -p <product_name> -r <release> -s <source_path> -l <os_list> -t <title> -c

Where:

-p <product_name>—Name of the KM package in the format, [A-Za-z0-9]. It also specifies the output name of the PPF file that will be created. The maximum number of character allowed in the product name is 10.

-r <release>—The version of the package to be used with BMC ProactiveNet in the format, vv.mm.rr

-s <source_path>—The path required to package member files. The files under source_path are copied to dest_path/products/product_name and zipped, and their respective entries are added under the files section of the ppf. The ppf and cat file are located at dest_path/Products/product_name, and a copy of the PPF is also placed in dest_path/Index/.

-l <os_list>—(Optional.) Comma separated list of OS types. The supported values are: AIX, SOLARIS, HP, LINUX, WINDOWS, ALL, ALL-UNIX. If you have not specified any operating system type, by default, ALL is considered as the value.

-t <title>—(Optional.) Product name (within double quotes) to be used in the BMC ProactiveNet Central Monitoring Repository. If you have not specified the product name, by default the name of the KM package (value of the -p switch) is considered as the value.

-c—(Optional.) Print copyright details

Here is an example of creating a BAP image for a custom KM, XOM:

 

 

$. /pcig-64 -s XOM/ -p XOM -t "PATROL for XOM" -r 1.0.00

prearing PPF [HEADER] section...

Loading files for packaging...

7 files prepared for packaging.

Preparing PPF [FILES] section...

Generating PPF file... bmc_products/Index/XOMs.km.ppf...

Generating AT file... bmc_products/Products/XOMskm/XOMskm.cat...

Here a BAP image for XOM KM will be created with the name "PATROL for XOM",  and the version 1.0.00. After you run the above command, the bmc_products folder will be created in the parent directory (temporary folder).

$ls -ltr

total 84

-rwxr-xr-x 1 wasbld bmc 74358 Jan 8 19:20 pcig

drwxr-xr-x 4 wasbld bmc 2048  Jan 8 20:30   XOM

drwxr-xr-x 4 wasbld bmc 2048  Jan 8 20:40   bmc_products

The bmc_products folder contains files required for building and packaging the KM. To list the files created for building and packaging the KM, run the find bmc_products -type f command.

 

Example:

c$ find bmc_products -type f

bmc_products/Index/XOMs.ppf

bmc_products/products/XOMs.km/XOMs1.gz

bmc_products/products/XOMs.km/XOMs2.gz

bmc_products/products/XOMs.km/XOMs3.gz

bmc_products/products/XOMs.km/XOMs4.gz

bmc_products/products/XOMs.km/XOMs5.gz

bmc_products/products/XOMs.km/XOMs6.gz

bmc_products/products/XOMs.km/XOMs7.gz

bmc_products/products/XOMs.km/XOMskm.ppf

bmc_products/products/XOMs.km/XOMskm.cat

bmc_products/imageinfo.000000-000000

c$ find bmc_products -type f

bmc_products/Index/XOMs.ppf

bmc_products/products/XOMs.km/XOMs1.gz

bmc_products/products/XOMs.km/XOMs2.gz

bmc_products/products/XOMs.km/XOMs3.gz

bmc_products/products/XOMs.km/XOMs4.gz

bmc_products/products/XOMs.km/XOMs5.gz

bmc_products/products/XOMs.km/XOMs6.gz

bmc_products/products/XOMs.km/XOMs7.gz

bmc_products/products/XOMs.km/XOMskm.ppf

bmc_products/products/XOMs.km/XOMskm.cat

bmc_products/imageinfo.000000-000000

Run the following command to see the values created in the PPF file:

$ more bmc_products/Index/<KM file name>skm.ppf

Example:

$ more bmc_products/Index/XOMskm.ppf

[HEADER]

PRODUCT=XOMskm

PKGNAME=XOM-KM-Application_Classes

VERSION=1.0.00

VERSION_COMPATIBILITY=ALL

BOOK=PATROL Knowledge Modules

DESC=PATROL for XOM

RELEASEVER=3.4, 3.5, 7.1, 7.2, 7.4

OSLIST=all

PRODUCT_FAMILY=PATROL

INFRASTRUCT_DESIGNATOR=PAT, PAV, PAA, PWN

ISKM=1

PKG_SIZE=29321

PKG_LOCALE=

AUTOSELECT

SEQUENCE=10000

[END HEADER]

 

[FILES]

./lib/knowledge/XOM_Performance.km;Y;;;644;all||

./lib/knowledge/XOM_Performance.kml;Y;;;644;all||

./lib/knowledge/XOM_Perf_Disks.km;Y;;;644;all||

./lib/knowledge/XOM_Perf_Disk_CONTAINER.km;Y;;;644;all||

./lib/knowledge/XOM_Perf_MSSQL_Locks.km.km;Y;;;644;all||

./lib/knowledge/XOM_Perf_MSSQL_Locks_CONTAINER.km.km;Y;;;644;all||

./XOM/XOM.cfg;Y;;;755;all

 

The BAP image of the custom KM will be created in a zipped file, and you can import this into BMC Performance Management Repository.

 

If you have in your KM code any calls to pconfig function (either to get or to write any values), as the structure of the /ConfigData/<KM name> branch has changed with respect to pure PATROL environment (without BPPM/CMA), then you will need to edit the KM files accordingly.

 

Here’s an example:

 

In a custom KM there is a file named MS_WATCH.km.

Within that file I can see below line:

 

    preconf=trim(pconfig (\"GET\", \"/OracleConfig.\".sid.\".FilterExcl\"),\" \", 3);\

 

Usually in the pconfig call you needed to pass the function (GET in this case) and the config var (/OracleConfig.\".sid.\".FilterExcl) to get its value.

 

As pconfig vars in 9.5 coming from policy configuration are containing different structure: /ConfigData/<KM name> ... , if within your code you are accesing the config vars from the custom KM then you would need to edit your KM files to accomplish with this new structure.

 

The above example may not be a good example because it seems it is accessing a config var from Oracle KM and this may not change when converting to CMA, but for instance, if the variable you would have in your code was as below:

    preconf=trim(pconfig (\"GET\", \"/MyOwnKM.\".sid.\".FilterExcl\"),\" \", 3);\

 

Then you should probably need to edit it when converting it to CMA to be like below:

    preconf=trim(pconfig (\"GET\", \"/ConfigData/MyOwnKM.\".sid.\".FilterExcl\"),\" \", 3);\

 

The same should happen with any pconfig calls with REPLACE function.

 

Managing the repository

Through BMC ProactiveNet Central Monitoring Administration, you can import new and updated monitoring components to the Central Monitoring Repository. You can also delete components that are not used in installation packages.

You can do the following kinds of imports:

 

Import Type    Description

Full repository    The entire repository with the most up-to-date BMC PATROL components and monitoring solutions. The repository files are imported from the following compressed files. For details about the contents of each file, see  BMC ProactiveNet Central Monitoring Repository overview.

 

•    9.6_base-yyyymmdd-hhmmss.zip (where yyyymmdd-hhmmss is the date and time of the repository image), typically imported with BMC ProactiveNet Central Server installation.

•    9.6_extended-yyyymmdd-hhmmss.zip (where yyyymmdd-hhmmss is the date and time of the repository image), typically imported after installation, using the procedure described below.

 

Single solution    A single solution for a specific update or to replace a deleted file. The solution must be located on the local computer from which you are running the Central Monitoring Administration web-based console.

 

Custom solution    A solution that is customized for specific environments or requirements. The solution must be located on the local computer from which you are running the Central Monitoring Administration web-based console.

See Building a PATROL Knowledge Module Developers Guide for details.

 

Before you begin

If you want to import the entire repository, first download Central Monitoring Repository files from the BMC Electronic Product Distribution (EPD)  facility, or copy the files from your installation kit, to the BMC ProactiveNet Central Server file system.

 

To import the full repository

1.    In the navigation pane of Central Monitoring Administration, click the Repository drawer and select Manage Repository.

2.    Click Import.

3.    In the Import a New Solution dialog box, select Full repository and click Import.

4.    Select the repository file (9.x_base-yyyymmdd-hhmmss.zip or 9.x_extended-yyyymmdd-hhmmss.zip) from the BMC ProactiveNet Central Server file system, and click Extract.

The selected archive file is imported to the repository and extracted. You can close the window during the import process.

 

To import a single or custom solution

1.    In the navigation pane of Central Monitoring Administration, click the Repository drawer and select Manage Repository.

2.    Click Import.

3.    In the Import a New Solution dialog box, select Single solution or Custom solution.

4.    Browse to a source file in one of the following formats: zip, tar, or tar.gz.

The solution must be located on the local computer from which you are running the Central Monitoring Administration web-based console.

5.    (Custom solution, only)provide the following details:

 

•    Custom solutions name: The name of the custom solution, as it will be displayed in Central Monitoring Administration.

•    Custom solution version: The version number for the custom solution. Values in the first two version boxes are required.

6.    Click Import.

The selected archive file is imported to the repository and extracted. You can close the window during the import process.

 

In Central Monitoring Administration 9.0, some items might not appear in the Monitor Configuration screen even after importing both the BMC ProactiveNet 9.6 base and extended repositories. For more information, see Knowledge Base article KA408417 (Support logon ID required).

 

To delete components from the Central Monitoring Repository

1.    In the navigation pane of Central Monitoring Administration, click the Repository drawer and select Manage Repository.

2.    Select one or more of the components that are not used in an installation package.

The column Used within installation packages lists the number of installation packages that use the component.

3.    Click Delete and click Yes to confirm the deletion.

 

If you have any issues with customized KMs being imported into BPPM or managed through the CMA, please view the Webinar video and if problems persist, please contact BMC Support.

 

Newly Published Knowledge Articles - New Content has been added over the last month!

KA402252 - Is it possible to export CMA policies from one BPPM server to another?

KA417462 - Installation of BPPM 9.5 SP1 fails with following message in install log "Issue with finding server installation from ProductRegistry.xml file, trying with the windows registry"

KA417560 - Why an Integration Service Node (ISN) 9.5 is appearing as "Unknown:0" in BPPM CMA console?

KA417771 - Seeing MC_CELL_PROCESS_ERROR event with msg slot *** BUILTIN 450 *** recorded_arg/4 : The argument descriptor and recorded term have an incompatible structure.

KA417878 - A database rebuild is failing with "SQL error: User 'DBA' has the row in 'PARTITION_CNTL' locked"

Popular Knowledge Articles

KA352096 - Unable to delete PATROL Adapter from ProactiveNet Admin Console

KA345591 - dbsrv.exe process crashed with an assertion failure

KA346342 -On Windows 2008 BPPM server 'pw system status' shows mcell as !Not Running! even though the cell is running

KA349542 - How to monitor the connectivity status between Patrol Agent and Integration Service (Pproxy Service)? 

KA373446 - Steps to convert AWF adapter into Manual adapter

 

DON’T MISS A GREAT OPPORTUNITY: Upcoming Webinars

Check out the details here: BMC ProactiveNet Performance Management (BPPM) 9.5 Best Practices Webinar Series

Upcoming Webinar topics include:

•    High Availability & Disaster Recovery (November 2014)

 

Sign up now by accessing the link above. Then click on the topic of interest and sign up for the Webinar. These are 90 minute sessions designed to help you get the most of out the product.

 

 

Looking for a previous blog posting?

Find them here:  BMC TrueSight Support Blogs

 

Feedback1.jpg

 

Feedback Request:

Are these blogs helpful to you? We want to hear from you. Let us know what you think or what topics you would like presented in our blog.

Share This:

We all like BPPM and its event management, policies, integrations, and notifications, but what do we make of all this information? BMC is proud to say that we offer great options for BPPM Reporting. We have some basic BPPM Server reporting and then we have more expansive BMC ProactiveNet Performance Management Reporting option. Since we just had a Webinar on the issue, why not follow up to cement your understanding. If you missed the Webinar, you can view the details here BMC ProactiveNet Performance Management (BPPM) 9.5 Best Practices Webinar Series

 

BMC ProactiveNet Performance Management Reporting is an advanced reporting platform. It uses the SAP® BusinessObjects Enterprise product as the host for BMC ProactiveNet Server to administer and publish reports. It also uses Oracle® Database as the application database. BMC ProactiveNet Performance Management Reporting contains templates for impact reports and event reports. It also contains a universe and one sample report to allow you to create ad-hoc performance reports.

 

•Impact report templates — display data based on a service's availability, failures, repairs and incidents, and the time related to each.

•Event report templates — display operator response time to an event, event counts, top event sources, and other event details.

•Performance reports — allows you to create ad-hoc reports based on devices, instances, monitor metadata, and group data.

 

Data for these templates is obtained from the Oracle database. BMC ProactiveNet Performance Management Reporting also enables you to create ad-hoc reports and offers more flexibility when compared to BMC Event and Impact Reporting.

 

Reporting Components

There are several different pieces involved in the Reporting within BPPM. Each component is needed to produce reports. Let’s take a quick look at the components:

Oracle Database

BMC ProactiveNet Report Engine collects component data and status change events and stores them in the Oracle database

 

BMC ProactiveNet Report Engine

The Report Engine aggregates events and component status changes from one or more BMC ProactiveNet servers. It also aggregates and summarizes performance data and stores it in Oracle database. The Report Engine periodically summarizes events and impact and performance data according to the reporting needs. For event reporting, you must configure all the instances of BMC ProactiveNet cells to propagate events to BMC ProactiveNet Report Engine and eventually into the Oracle database.

 

 

SAP BusinessObjects Enterprise

The SAP BusinessObjects Enterprise Central Management Server (CMS) contains reporting for the BMC Service Assurance products, report templates, and the SAP BusinessObjects report repository database. This database is separate from the Oracle database


InfoView web client
BMC ProactiveNet Performance Management Reporting uses the SAP BusinessObjects InfoView web client to view, generate, and save reports. Using a browser, you can view reports and store them in a common area in the SAP BusinessObjects Enterprise CMS repository database, or you can store them in a personal area that only you can access. InfoView also provides search tools to locate saved reports.

 

 

 

Requirements for installing Reporting

When you are ready to dive into BPPM Reporting, take a look here for your System Requirements followed by hardware recommendations and finally an installation.

 

 

https://docs.bmc.com/docs/display/public/bppmreporting952/System+requirements

https://docs.bmc.com/docs/display/public/bppmreporting952/Hardware+recommendations

https://docs.bmc.com/docs/display/public/bppmreporting952/Installing

 

Here’s a good visual of the order of installation and configuration

Reporting can use a lot of resources and can be taxing on your system. So we recommend you follow the retention and tuning guidelines outlined here: Reporting Performance Tuning Tips 

 

Reporting FAQs

 

Can all Reporting components be installed on the same server? This is the most common question we have.

Unfortunately, the answer is no, the components cannot all be installed on the same server. The best way to explain the installation scenarios is to review the details here Deployment architecture

 

Where do I get a license for SAP® BusinessObjects?

If you do not have a license key, you can obtain one through the BMC Electronic Product Distribution website

https://docs.bmc.com/docs/display/public/bppmreporting952/Licensing+information

 

When installing multiple Reporting Engine instances with one single Oracle schema, can we use the standard Oracle scripts? Does the installer overwrite the DB every time it runs?

The reference this answer is in the "Installing BMC ProactiveNet Report Engine for Oracle database" document under the section "To install BMC ProactiveNet Report Engine on the second or subsequent computers" there is a note: "You do not have to create a table space and a database user for the second or subsequent computers because, the other instances of Report Engine use the same database user."

 

Error during upgrade/install of BPPM Reporting Engine: “Invalid database credentials for user "xxxx". Configure database by using "create_BPPMR_user_tablespaces.sql".

The error indicates that  the pre-requisite steps are not performed before upgrade or install. Customers need to run the script create_BPPMR_user_tablespaces.sql  (available in the 9.5.02 installable image) before launching the installer for upgrade/installation. "

 

The BMC ProactiveNet Report Engine installation files contain the create_BPPMR_user_tablespaces.sql script that you use to create the table spaces and the user. To run the script, you need a user with SYSDBA privileges. A successful execution of the script creates the required table spaces and a user with appropriate rights.
https://docs.bmc.com/docs/display/public/bppmreporting952/Creating+table+spaces+and+user+on+Oracle+database

Please refer section "General prerequisites and recommendations" from the BMC ProactiveNet Performance Management Reporting 9.5.02 document. While running the create_BPPMR_user_tablespaces.sql script , it will prompt for the report engine DB credentials, you need to provide the existing RE DB user credentials if upgrading. Basically this script creates the additional read only user and table spaces required for 9.5.02 release.

 

 

Is there a way to filter the BPPM data, for example if I collect CPU/Memory/Disk data from Patrol Agents, but I only want to  store and the create reports for only CPU and Memory, or only for a subset of Agents, is this possible?
Indeed it is! Users can create an External Report attribute set

An External Report attribute set enables the following:

Filtering capabilities — performance data is transferred from BMC ProactiveNet Server to the report engine, and performance reports are generated only on those attributes you have selected.

 

To create an External Report attribute set:

On the BMC operational console, go to Options > Administration > Attribute Sets > Edit.

Click the relevant option:

For a new attribute, click Add in the AttributeSet Administration screen.

To edit an existing attribute, click Edit. Click Add Attributes to add more attributes.

On the Add Attribute Set screen, select the Attribute Set type External Report.

Select the Monitor Type. Select all monitor types corresponding to the attributes to be grouped.

Use the Shift and Ctrl keys to make multiple selections. To locate a specific monitor, use the Search For field.

Click Next.

Select the attributes to be grouped from under each of the monitor types in the Attributes section.

Use the Shift and Ctrl keys to make multiple selections. To locate a specific attribute, use the Search For field.

Click Next.

Specify a name for the attribute set.

Select the attributes to be included by selecting the corresponding check boxes in the Select column.

Click Finish. The new External Report attribute set is available for use

Registering the BMC ProactiveNet Server

After you create an attribute set, you must register the BMC ProactiveNet Server. To register the BMC ProactiveNet Server, enter the following command: bpmr_config -add serverName

 

Newly Published Knowledge Articles - New Content has been added over the last month!

KA416080 - The cmapolicymigration script is not exporting any policies.

KA416061 - Unable to access the BPPM 9.5 online help in Operations Console, Administration Console and CMA Console.

KA416518 - Offline/localhelp in BPPM 9.5 is not working for certain help pages in BPPM CMA console.

KA416652 - BPPM 9.5 SP1 - The BPPM Admin Console is displaying duplicate DDA folders.

KA416679 - LDAP logins are failing but is resolved after restarting the jserver.

KA416747 - Is it possible to increase the font size for the BPPM Operations Console?

KA417140 - What is the isAppendBPPMName parameter used for in IBRSD 9.5?

 

Popular Knowledge Articles

KA349830 - Error dialog "Close failed for 1 event(s) with Internal ID(s): EventID" when attempting to close ProactiveNet events using ProactiveNet Operations Console

KA355447 - BPPM Patrol Adapter troubleshooting 

KA350291 -The BPPM self monitoring KM (MTM KM) will not discover and monitor after installation.

KA382011 - I am unable to send events directly from Patrol Agent v9 to cell.

KA321220 - How can I customize the Operations console to include a custom logo?

 

 

DON’T MISS A GREAT OPPORTUNITY: Upcoming Webinars

Check out the details here: BMC ProactiveNet Performance Management (BPPM) 9.5 Best Practices Webinar Series

Upcoming Webinar topics include:

 

•    Configuring for Advanced Thresholds and Abnormalities (September 30th 2014)

•    Configuring Simple Service Modeling & PCA (October 2014)

•    High Availability & Disaster Recovery (November 2014)

 

Sign up now by accessing the link above. Then click on the topic of interest and sign up for the Webinar. These are 90 minute sessions designed to help you get the most of out the product.

 

 

Looking for a previous blog posting?

Find them here:  BMC TrueSight Support Blogs

 

Feedback1.jpg

 

 

 

 

 

Feedback Request:

Are these blogs helpful to you? We want to hear from you. Let us know what you think or which topics you would like presented in our blog.

Share This:

Are you using BPPM 9.0x or earlier?
If so are you seeing duplicate devices?

 

The instances of duplication in BPPM have been on the rise here in the Support community. The BPPM Console is displaying duplicate devices. You’re not seeing double and please do not adjust your monitor; this is a known issue with BPPM and it is documented as to how to fix it. We also recommend upgrading to BPPM 9.5 as soon as possible to avoid the issue.

 

So what is this duplicate device stuff anyhow? Let’s take a deeper look at the issue:

 

The issue has to do mainly with the way devices are handled in BPPM. See BMC ProactiveNet Server defines an entity that it can monitor as a device. Because BMC ProactiveNet Server collects data from many sources by using different methods, monitored entities are presented to BMC ProactiveNet Server as devices in multiple ways. BMC ProactiveNet Server has algorithms to convert the information presented about entities into devices, to determine whether two or more pieces of data refer to the same entity, and to consolidate those entities into a single device. However, due to the divergent nature of the data collection process, BMC ProactiveNet Server may not always determine that multiple entities are in fact referring to the same device. As a result, duplicate devices can show up in BMC ProactiveNet Server, but you can prevent most of such scenarios by using configuration settings.

 

A wide range of data sources can create devices in BMC ProactiveNet Server, and each source can be configured in different methods and can interpret data in a different style. This means there are many causes of duplicate devices so please take the time to review them all. This results in a situation where data flows into BMC ProactiveNet Server about a given device in multiple formats such as IP address, hostname, and FQDN. BMC ProactiveNet Server uses the best possible algorithm to identify that it is the same device that is presented in multiple formats by comparing the UUIDs if the device is a virtual machine in VMware, reconciliation IDs if the device is from BMC Atrium CMDB, and FQDNs if the device is across data sources. The algorithm can be summarized as follows:

  • If information about the two devices comes in through the BMC PATROL Adapter, compare the FQDN property presented by the BMC PATROL Agent. If the strings match, the devices are consolidated.
  • If the two devices are VMware virtual machines, compare their UUIDs. If the strings match, the devices are consolidated.
  • If information about the two devices comes in from BMC Atrium CMDB, compare their CMDB reconciliation IDs.  If the strings match, the devices are consolidated.
  • If information about one device comes from BMC PATROL Agent and that about another from BMC Atrium CMDB, compare their component alias values. If the strings match, the devices are consolidated.
  • If information about one device comes from BMC PATROL Agent and that about another from BMC Performance Manager Portal, compare their hostname and FQDN values. If the strings match, the devices are consolidated.

 

Tips for Avoiding Duplicate Devices:

 

  • Ensure that the /AgentSetup/integration/publishHostName variable is set as the FQDN of the host
  • Because BMC ProactiveNet Server is case sensitive, ensure that the host names are set in the same case similar to FQDN
  • Use FQDN of a device rather than the short name of it.

 

We see many different scenarios where duplicate devices are detected within BPPM. Here are the main areas we see issues:

 

 

Scenarios where multiple BMC PATROL AGENTS collect data for the same device

BMC PATROL Agent presents the details of each computer on which it is running as a device. If any of these computers is also monitored by another BMC PATROL Agent, a scenario arises where information about the same device comes to BMC ProactiveNet Server through different agents. The deployment architecture for this scenario to occur can be as follows:

  1. A BMC PATROL Agent is running on a virtual machine. The virtual machine is also monitored using another BMC PATROL Agent, which is running on another computer.
  2. A BMC PATROL Agent is running on a computer. This computer is also remotely monitored using another BMC PATROL Agent, which is running on another computer by using the remote monitoring capability of Windows KM or Unix KM.
  3. A BMC PATROL Agent is monitoring a virtual machine, and another BMC PATROL Agent is remotely monitoring the same virtual machine by using the remote monitoring capability of Windows KM or Unix KM remote.


Devices with Hostname and FQDN
BMC ProactiveNet Server displays duplicate devices when the hostname and FQDN (for example, xyz and xyz.acme.com) for the same device are found. It can happen when a device is represented with the short name through one route and with FQDN through another route. BMC PATROL Agent versions earlier than 9.0.00 publish themselves with the short name (hostname). For versions 9.0.00 or later, BMC PATROL Agent behavior can be changed to publish FQDN by using /AgentSetup/integration/useFQDNHostName variable and set its value to yes. Also, if a computer is configured with no DNS configuration but just the hostname, the device is represented with the short name.

 

Device with different DNS subdomains
BMC ProactiveNet Server displays duplicate devices when devices with different DNS subdomains are found, for example, xyz.acme.com and xyz.sub.acme.com.

 

Input value of BMC ProactiveNet Integration Service is different from the value returned by the BMC PATROL Agent
BMC ProactiveNet Server displays duplicate devices when the input value of BMC ProactiveNet Integration Service is different from the value returned by BMC PATROL Agent through the /AgentSetup/integration/publishHostName variable (BMC PATROL Agent is installed on BMC ProactiveNet remote agent with integration service enabled).

 

Token ID value is different for the same device name
BMC ProactiveNet Server displays duplicate devices when the token ID values are different for the same device.

 

Remote Monitoring: VSM KM monitoring a virtual machine and BMC PATROL Agent installed on the virtual machine
BMC ProactiveNet Server displays duplicate devices when the BMC PATROL Agent and the VSM KM running on a different BMC PATROL Agent present the same name in different formats (short name or FQDN).

 

Same device names (short name or fqdn) presented in different cases (for example: uppercase, lowercase, or mixed case)
BMC ProactiveNet Server displays duplicate devices when devices with the same name (short name or FQDN) are presented in different cases.

 

Different device DNS names for the same device, before and after powering on the virtual machine
This scenario was observed in BMC ProactiveNet Server version 8.5 SP4 but not in BMC ProactiveNet Server version 8.6 SP2. BMC ProactiveNet Server displays duplicate devices when the devices have different DNS name before and after the virtual machine is powered on.

 

BMC PATROL Agent added on different ports in manual mode using automatic registration with integration
BMC ProactiveNet Server displays duplicate devices when BMC PATROL Agent is added in manual mode and using automatic registration with integration.

 

Scenarios where BMC PATROL Agents and BMC Performance Manager Portal collect data for a device
As a general best practice, it is best to add elements to BMC Performance Manager Portal for monitoring by using FQDN. This ensures that when a device is imported to BMC ProactiveNet Server, it uses the FQDN for device creation. If the information about the device comes from another route (for example, BMC PATROL Agent) by using FQDN, the device is consolidated.

 

Device names from BMC PATROL agent/BMC Performance Manager Portal and alias name from BMC Atrium CMDB are different

BMC ProactiveNet Server displays duplicate devices when device names from BMC PATROL Agent/BMC Performance Manager Portal and the alias name for the same device in BMC Atrium CMDB are different.

 

Save device names (short name or FQDN) presented in different cases (for example: uppercase, lowercase, or mixed case)
BMC ProactiveNet Server displays duplicate devices when devices with the same name (short name or FQDN) are presented in different cases.

 

Scenarios where BMC PATROL Agents, BMC Performance Manager Portal, or SCOM and BMC Atrium CMDB collect data for a device

Device having different reconciliation IDs during BMC ProactiveNet Server and BMC Atrium CMDB sync
A device can have different reconciliation IDs mostly due to bad reconciliation. BMC ProactiveNet Server displays duplicate devices when a device has different reconciliation IDs during BMC ProactiveNet Server and BMC Atrium CMDB sync. The duplicate reconciliation IDs most likely exist in BMC.ASSET dataset.

 

In BMC Atrium CMDB, reconciliation ID is used to identify the same CI across multiple datasets. The reconciliation ID is set during the identification phase of reconciliation in BMC Atrium CMDB. If the identification rules in BMC Atrium CMDB fail to identify a CI that already exists, BMC Atrium CMDB can generate a new reconciliation ID for the CI, which results in duplicate CIs in the BMC.ASSET dataset with different reconciliation ID. In this case, the problem is with the identification rules in BMC Atrium CMDB or the provider of that data to BMC Atrium CMDB such as BMC Atrium Discovery and Dependency Mapping, SCOM, or BMC Server Automation.

 

Devices created in BMC Atrium CMDB first and then synced through BMC PATROL Agent Adapter
The following table explains different scenarios that can create duplicate devices:

BMC Atrium CMDB

BMC PATROL Agent

Result

FQDN

IP Address

Creates duplicate device

FQDN

Hostname

Creates duplicate device

Hostname

IP Address

Creates duplicate device

Hostname

FQDN

Creates duplicate device

 

Devices created in BMC Atrium CMDB first and then synced through BMC Performance Manager Portal Adapter
The following table explains different scenarios that can create duplicate devices:

BMC Atrium CMDB

BMC Performance Manager Portal

Result

FQDN

IP Address

Creates duplicate device

FQDN

Hostname

Creates duplicate device

Hostname

IP Address

Creates duplicate device

Hostname

FQDN

Creates duplicate device

 

Devices created in BMC Atrium CMDB first and then synced through SCOM Adapter
The following table explains different scenarios that can create duplicate devices:

BMC Atrium CMDB

SCOM

Result

FQDN

IP Address

Creates duplicate device

FQDN

Hostname

Creates duplicate device

Hostname

IP Address

Creates duplicate device

Hostname

FQDN

Creates duplicate device

 

Devices with different component aliases in BMC Performance Manager Portal and BMC Atrium CMDB
BMC ProactiveNet Server displays duplicate devices when a device has different component aliases in BMC Performance Manager Portal and BMC Atrium CMDB.

 

Guidelines to prevent duplicate CIs during data synchronization between BMC Atrium Discovery and Dependency Mapping and BMC Atrium CMDB
The following guidelines must be followed to ensure that the data synchronized from BMC Atrium Discovery and Dependency Mapping to BMC Atrium CMDB does not generate duplicate CIs in BMC.ASSET dataset or duplicate devices in BMC ProactiveNet Server: Configure CI filtering in BMC Atrium Discovery and Dependency Mapping to ensure that the quality data is synchronized. Only synchronize CIs from BMC Atrium Discovery and Dependency Mapping to BMC Atrium CMDB that do not have null values for attributes that are used in the identification rules of reconciliation process. Ensure that the BMC Atrium Discovery and Dependency Mapping resolve FQDNs of its devices against the primary DNS domain (xyz.acme.com) because BMC ProactiveNet Server is configured to resolve FQDNs against the primary DNS domain.

 

You can create custom synchronization mappings in BMC Atrium Discovery and Dependency Mapping to automatically create component aliases within BMC Atrium CMDB, for example, converting the FQDN to lowercase, uppercase, or mixed case, constructing new component aliases from other dynamic CI attributes, or even setting static component aliases.

 

Best Practices for BMC Atrium Discovery and Dependency Mapping to avoid duplicate devices
The information of a normal computer system coming from BMC Atrium Discovery and Dependency Mapping has the name of the server and domain as a separate field, and BMC ProactiveNet Server consolidates the entries based on it. You can also use an alias entry or entries with host name and domain for the manual computer system CIs.

For example, some attributes for the discovered server at acme.com are as follows:

 

For the network-attached storage devices, if the ComponentAliases field is blank, the best practice is to be consistent with the host name (for example, xyz) and the domain name (for example, acme.com) of the discovered server.

To see examples of the scenarios mentioned above or for the entire document regarding Duplicate Devices, please download it from here- http://documents.bmc.com/supportu/documents/88/88/298888/298888.pdf

 

How to clean up duplicate devices in BPPM

BMC has created a stale cleaner script which will clean up the devices from the database level. The stale cleaner modifies the BPPM database and identify and remove duplicate devices. The stale cleaner requires stopping the BPPM server and starting only the BPPM database and the cell.

 

 

Here are the complete details from the readme file for the stale cleaner script so you can be familiar with the steps needed to run the script. The script applies to both Sybase and Oracle and can be run on UNIX or Windows. The script should only be run at the recommendation of BMC Support. Therefore, if you see issue with duplication, please let us know so we can recommend the best way to manage the type of duplication being seen in BPPM. The stale cleaner location will be sent to you on an as needed bases. Given the power of the script Support needs to review the situation and determine if the script should be run.

 

*** NOTE *** This script is not applicable for BPPM 9.5 and must not be run against that version ***
** NOTE ** If BPPM is integrated with CMDB then only stale instance cleanup is supported.**

  1. To find stale instances and stale autodiscovered devices, the following can be executed with BPPM server running:

a. Windows BPPM server:

- If a Sybase DB is used:
launchScript.bat -object Instance
launchScript.bat -object Device
- If an Oracle DB is used:
launchScript.bat -object Instance -host <ORACLE_SERVER_HOSTNAME> -port <ORACLE_SERVER_PORT>  -sid <SID> -user <USERNAME> -password <PASSWORD> -dbtype ORACLE

               launchScript.bat -object Device -host <ORACLE_SERVER_HOSTNAME> -port <ORACLE_SERVER_PORT>  -sid <SID> -user <USERNAME> -password <PASSWORD> -dbtype ORACLE              

Note: In the single Oracle database instance, need to specify the SID or ServiceName of the instance in <SID>. In the Oracle RAC system, need to specify a ServiceName which exists for the entire Oracle RAC system in <SID>.

b. Solaris/Linux BPPM server:
- Source the BPPM environment:
- Bourne/Bash
. /usr/pw/pronto/bin/.tmprofile
- C shell:
source /usr/pw/pronto/bin/.tmcsh

   - Make the script executable:
chmod 755 launchScript.sh

- If a Sybase DB is used:
./launchScript.sh -object Instance
./launchScript.sh -object Device

  - If an Oracle DB is used:

      ./launchScript.sh -object Instance -host <ORACLE_SERVER_HOSTNAME> -port <ORACLE_SERVER_PORT> -sid <SID> -user <USERNAME> -password <PASSWORD> -dbtype ORACLE

      ./launchScript.sh -object Device -host <ORACLE_SERVER_HOSTNAME> -port <ORACLE_SERVER_PORT> -sid <SID> -user <USERNAME> -password <PASSWORD> -dbtype ORACLE              

Note: In the single Oracle database instance, need to specify the SID or ServiceName of the instance in <SID>. In the Oracle RAC system, need to specify a ServiceName which exists for the entire Oracle RAC system in <SID>.

2. The output will be written to the following files:
a. BPPM-DiscvStaleObjects-Inst.txt - contains a list of the stale instances
b. BPPM-DiscvStaleObjects-Dev.txt - contains a list of the stale autodiscovered devices

3. To cleanup stale instances and stale autodiscovered devices, please perform the following:
a. Stop BPPM server with 'pw sys stop' command.

b. Once BPPM server is stopped (verify with 'pw p l' command), please take a backup of the pw\server\var\ directory. If Sybase database is used, take a backup copy of the pronto.log and storm*.db files in pw\sybase directory. If Oracle database is used, contact the DBA to ensure a backup is performed of the database.

c. Start just the database and the cell. The cell can be started with 'pw p s mcell' command. If Sybase database is used, it can be started with 'pw p s dbsrv' command. Verify that both the cell and database are running with 'pw p l' command.

d. Windows BPPM server:
- If a Sybase DB is used:
launchScript.bat -object Instance –cleanup
launchScript.bat -object Device -cleanup

   - If an Oracle DB is used:

               launchScript.bat -object Instance -host <ORACLE_SERVER_HOSTNAME> -port <ORACLE_SERVER_PORT>  -sid <SID> -user <USERNAME> -password <PASSWORD> -dbtype ORACLE -cleanup

               launchScript.bat -object Device -host <ORACLE_SERVER_HOSTNAME> -port <ORACLE_SERVER_PORT>  -sid <SID> -user <USERNAME> -password <PASSWORD> -dbtype ORACLE -cleanup

Note: In the single Oracle database instance, need to specify the SID or ServiceName of the instance in <SID>. In the Oracle RAC system, need to specify a ServiceName which exists for the entire Oracle RAC system in <SID>.

e. Solaris/Linux BPPM server:
- Source the BPPM environment:
- Bourne/Bash
. /usr/pw/pronto/bin/.tmprofile

      - C shell:
source /usr/pw/pronto/bin/.tmcsh

   - If a Sybase DB is used:
./launchScript.sh -object Instance –cleanup
./launchScript.sh -object Device -cleanup

   - If an Oracle DB is used:

      ./launchScript.sh -object Instance -host <ORACLE_SERVER_HOSTNAME> -port <ORACLE_SERVER_PORT> -sid <SID> -user <USERNAME> -password <PASSWORD> -dbtype ORACLE -cleanup

      ./launchScript.sh -object Device -host <ORACLE_SERVER_HOSTNAME> -port <ORACLE_SERVER_PORT> -sid <SID> -user <USERNAME> -password <PASSWORD> -dbtype ORACLE -cleanup

Note: In the single Oracle database instance, need to specify the SID or ServiceName of the instance in <SID>. In the Oracle RAC system, need to specify a ServiceName which exists for the entire Oracle RAC system in <SID>.

f. Once the script has completed, please start BPPM server with 'pw sys start' command.


If you find any discrepancies after executing the script:
Stop BPPM server with 'pw sys stop' command.
Restore the backups taken in step 3b above:

a. the database
b. the pw\server\var directory
Start BPPM server with 'pw sys start' command.

 

Newly Published Knowledge Articles - New Content has been added over the last month!

KA414984 - With BPPM 9.5, is it possible to suppress the header when running a pw command?

KA415240 - Global records lost after upgrading cell from version 9.0 to version 9.5.

KA415434 - The Data Collection & Consistency Status Problem Report shows devices that have a filter policy applied.

KA415590 - After upgrading to BPPM 9.5, ALARM events are not visible in the ops console. Events for other event classes are seen ok.

KA415613 - The BPPM database size is very large

KA415588 - What happens to an Incident raised via IBRSD if the causal event is closed and then reopened?

KA415563 - Why is there no BPPM 9.5 Monitor the Monitor KM (MTM KM) ?

KA415372 - Receiving "Unable to process Application Class "PMG_GLOBAL_SETTINGS" from Patrol Agent" after configuring PATROL Agent in BPPM CMA 9.5.00.

KA414761 - Where can I find the PCIG utility documentation and files?

 

Popular Knowledge Articles

KA329164 - Is there a way to manually delete the auto-synced groups in ProactiveNet Server 8.x.xx?

KA356762 - How to check the data collection in BPPM database  

KA350291 -The tunnelproxy process is not running.

KA361627 - The installation of the ProactiveNet CMDB Extensions from BPPM 8.6.02 and 8.6.02.01 failed on Atrium (AR) version 7.6.04 SP2 

KA329355 - Will the data from the PATROL Adapter be deleted from the ProactiveNet database (Sybase) when the PATROL Adapter is deleted? 

 

 

DON’T MISS A GREAT OPPORTUNITY : Upcoming Webinars

Check out the details here: BMC ProactiveNet Performance Management (BPPM) 9.5 Best Practices Webinar Series


Upcoming Webinar topics include:

•    Configuring for Advanced Thresholds and Abnormalities (September 2014)

•    Configuring Simple Service Modeling & PCA (October 2014)

•    High Availability & Disaster Recovery (November 2014)

 

Sign up now by accessing the link above. Then click on the topic of interest and sign up for the Webinar. These are 90 minute sessions designed to help you get the most of out the product.

 

Looking for a previous blog posting?
Find them here: BMC TrueSight Support Blogs

 

Feedback1.jpg

Feedback:

Help us determine how we are doing. Use the rating system at the bottom of this blog to rate this post! Feel free to comment as well. We want to hear from you!

Filter Blog

By date:
By tag: