Skip navigation
Share:|

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

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

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

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

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

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

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

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!

Share:|

BPPM has many notification options and users can choose to receive events, SNMP traps, email notifications or all of the above.  Which notification method do you prefer? Events are key, but did you know those events can trigger email notifications? Some users prefer to receive email notifications when alerts are triggered. Users can setup email groups and then also setup rules for which notifications are sent. Having many options for notifications and alerts also leads to issues or problems with email notifications. The majority of email alerts issues are configuration issues with event policies or invalid SMTP server configurations, but there are a few other issues that we have seen.

 

Let’s highlight some of the types of questions we receive regarding email notifications.

 

How do I create an email group in BPPM when using Event Rules for notifications?

 

An email group is a group of email addresses by which event rule actions can be sent to an email group. The group consisting of email addresses is notified. You can add, modify, or delete any email group by accessing the Email Group Administration dialog box through the Email Group Administration button on the Event Rule Administration page. When setting up event rules, you must determine the way in which event notifications are sent.

 

 

BMC ProactiveNet can send event notifications through email when an event is generated. Event email messages contain the same information as the events viewed from the event Summary page. Email messages can be sent in HTML format.

Email notification, which includes the event listing, is similar to how it would be viewed from the BMC ProactiveNet Operations Console. If your email client supports HTML format, relevant graphs can be viewed.

 

Details of the SMTP Server to be used for email alerts are stored in pronet.conf under InstallationDirectory/pw/custom/conf:

 

pronet.api.emailer.smtp.host=mail.bmc.com

pronet.api.emailer.smtp.port=25

 

These entries are dynamically generated. Refrain from editing these without prior impact assessment. Any changes to these entries impact all mail-related BMC ProactiveNet actions (event notification/reports/alerts).

 

HTML event notifications contain partial GIFs of the event summary detail, along with the event graph. It is important that your ISP, email client, and network support HTML email messages. HTML format is preferred if your email client supports it. HTML provides for enhanced report layout and inclusion of graphs.

 

Similarly, the subject and body of a particular email alert can also be customized using Event Text Customization for Individual Event Rules.

 

To create or edit an email group

 

On the Event Rule Administration page, click the Email Group Administration tab.

On the Email Group Administration page, click Add.

Type the name of the group and list of email addresses.
Select the preferred email type from the list.

Click Add to add the email group.

Click Done to save the email group options.

Is it possible to customize the event text some email alerts?

 

Customizing the event text for email alerts


Event text customization enables you to insert event text for all email alerts. Certain event text customization variables are only available for ProactiveNet intelligent events. They are:

 

$EVENTID

$MC_LONG_MSG

$INSTANCE_NAME

$ABNORMALITY

 

When applied to external events, these variables have blank values.

 

For upgrade users

BMC ProactiveNet provides additional out-of-the-box variables, such as $Status, $MC_HOST, and $MC_PRIORITY for event text customization. See the table below for a complete list. Upgrade users cannot immediately select these additional variables. They have to add them manually. Upgrade users can enter the new variables that they need directly in the wizard.

 

To customize the event text

 

    Click the Options tab at the top-right of the BMC ProactiveNet Operations Console.

    On the Administration tab, choose Event Text Customization Edit link.

    On the Global Event Text Customization screen, customize the subject and body of the email alerts.

 

You can choose from among the following variables listed in the table below.

 

Variables for customizing the event text

EV1.jpgEV2.jpgEV3.jpg

Email alerts are not working!!!!???

 

What do you do when your email notifications are not working correctly? What are the locations to verify that alert email generation within BPPM is having issues? It appears that alerts are not being generated and email notifications being provided.

 

The first step would be to review the email settings and configure your computer to receive email messages from BPPM. See Preinstallation tasks in the online documentation.

 

The notification policy is configured to generate a notification email, but no email is being sent.

 

Notification email messages are not sent when the SMTP server is not installed or set up correctly. When the product is installed, part of the installation process locates the SMTP server. If an SMTP server is not installed before the product is installed, email notifications cannot be sent. If you have installed an SMTP server after the product was installed, run the following utility from C:\ProgramFiles\BMC Software\Impact\server\etc\cellName\kb\bin\w4, the product installation directory

 

There is a command "pw test_email". You can run this in the pw command window. Are there any errors in the output? You check the output file TestEmail.log under pw/pronto/tmp directory or send these logs to Support for further assistance:

\pw\pronto\tmp\TestEmail_hold.log

\pw\pronto\tmp\send_test_email.log

 

If the information above does not help, provide following information to Support via a Support ticket

- Output of pw viewhistory.

- Did the email work properly before?

- Did you make any changes recently?

Why do I receive email alerts from BPPM late? For example, the alert occurred at one time and I get the email alert about 45 minutes later.

 

If you have issues with delays in email you can enable EventActions debug and this will show in EventActions.log(under pw/pronto/logs/debug/).

 

You can use following pw command to enable the debug:

pw debug on -p jserver -s EventActions

 

Here is an example of messages seen in that log :

 

DEBUG 07/21 05:39:55 EventActions [AlarmAction-1] @ AlarmAction @ EmailAction: ASCII FULL Body >>> Device: mytester.myserver.com

Monitor Type: Windows System

Instance: mytester.myserver.com Windows System

Severity: CRITICAL

Status: OPEN

Message: Windows System Total CPU Utilization > 5% for 1 min. has been received from host mytester.myserver.com with severity CRITICAL

This will help to find the event and when it should have triggered a notification

In BPPM, email can be triggered by both the notification policy and the event rule setting. What is the difference between them?

 

Notification policies are set on the cell side, configured from the Admin Console, and can be set by the condition of cell specific class/ slot value etc, but the email content is in text format. If your notification should be set for external events which need to match criteria for class/slot value, then you need to use notification policy.

 

Email notifications are set by event rules on the Jserver side, configured from the User Console, and can be set by the condition of devices/monitors/attributes. So if your email notification is mostly for intelligent events that match condition of device/monitor/attribute then you can use an event rule.

 

Sometimes notifications based on event policies are duplicated

 

For example: The notification policy is triggered twice resulting in duplicate emails being received. This is the notification policy in baroc format:

IM_NOTIFICATION_POLICY;

data_handle=3013;

mc_udid='mc.pncell_BPPM.febd4be.0';

mc_creation_time=1340855486;

mc_modification_time=1345114354;

mc_modification_request_time=1345114354;

mc_modification_requestor=admin;

name=Proactivenet_error_event;

selector_name='Pnet_Agent.ProactiveNet_Agent_Event';

selector_class=PPM_EV;

selector_ecf='*Pnet_Agent.ProactiveNet_Agent_Event ($EV)';

notification_service=BASIC_EMAIL;

notify_targets=['BPPM_Admin@bmc.com'];

notify_source=ProactiveNet;

notify_subject_format='%s : %s : %s : %s';       notify_subject_slots=['$1.mc_host','$1.severity','$1.mc_object_class','$1.msg'];

notify_msg_format='.

HOST            : %s

IP-ADDRESS : %s

%s : %s

%s';  notify_msg_slots=['$1.mc_host','$1.mc_host_address','$1.mc_object_class','$1.mc_object','$1.msg']; when_slot='severity';

when_operator='within';

when_value='[MAJOR,CRITICAL]';

END

 

Duplicates are being triggered twice due to the absence of the notify_on_operations slot. That slot has default value of [OPEN]. The first email is sent because the status is within [OPEN]. The second email is sent because the severity is within [MAJOR,CRITICAL]. When  specifying a “slot, operator, value” option in a notification policy the notify_on_operation should be set to []. It is not possible however to set that in BPPM Administration console or in Impact Explorer. For the example policy in baroc format, create a new baroc file i.e. c:\data.baroc with following contents :

 

IM_NOTIFICATION_POLICY;

mc_udid='mc.pncell_ICTBPPM.febd4be.0';

notify_on_operations=[];

END

Then mposter this to the cell : mposter -n <cell> -d c:\data.baroc

 

If there are a large number of notification policies or notification policies are regularly being added then the above may not be practical. Another workaround is to modify pw\server\etc\<cell>\kb\classes\im_policies.baroc and change this line from :

 

notify_on_operations    : LIST_OF STATUS, default=[OPEN];

to :

notify_on_operations    : LIST_OF STATUS, default=[];

then recompile the KB and restart the cell.

 

BPPM 9.5 email issue:


When trying to send an email from BPPM 9.5 (either from the operations console or from an event rule) the email fails to be sent and one of the following errors is returned:

------------
GroupEmail - Email Group :Team Platform - Failed : Failed to send email to adm@yourcompany.com (file://test@yourcompany.com/). Reason :334 VXNlcm5hbWU6
Failed to send email to admin1@domail.com (file://admin1@domain.com/). Reason :334 VXNlcm5hbWU6
------------
E-Mail Details for Snapshot
Error occurred while sending mail to adm@yourcompany.com.
Exception Details: 535 5.7.0 authentication failed .
------------
Error occurred while sending mail to email@blabla.com
Exception Details: No authentication mechansims supported by both server and client.   
------------

We also see similar errors in the ProactiveNet.log file (this example is seen when sending an email using an event rule):

ERROR 05/20 11:56:24 EventActions [AlarmAction-5] 302536 Exception while executing Alarm Action
java.lang.Exception: 334 VXNlcm5hbWU6
at com.proactivenet.api.action.EmailAction.executeAlarmAction(EmailAction.java:189)
at com.proactivenet.api.action.NGPAbstractAlarmAction.execute(NGPAbstractAlarmAction.java:230)
at com.proactivenet.api.action.AADispatcher$Task.run(AADispatcher.java:90)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)

The 'pw test_email' cli is successful.

 

Here’s the fix:

1. Take a backup copy outside of the BPPM directories of the file..\Proactivenet\pw\apps3rdparty\javamail\mail.jar

2. Unzip the attached file to a temporary folder

3. Copy the extracted mail-1.3.3.jar file to ..\Proactivenet\pw\apps3rdparty\javamail on the BPPM Server

4. Rename mail-1.3.3.jar  in ..\Proactivenet\pw\apps3rdparty\javamail to mail.jar

5. Restart the BPPM Server processes (pw system start)

Defect QM001848727 with description "Sending of emails from Event Rules is not working after upgrading from BPPM 9.0 SP1 to 9.5" has been created to ensure this is fixed in a future release.

This fix information is found in our Knowledge Base:

"Failed to send email to XXXX. Reason :334 VXNlcm5hbWU6" or "Exceptions details : 535 5.7.0 authentication failed" when trying to send an email from BPPM 9.5 

 

 

These are just a few issues we have seen with sending email notifications within BPPM. Most of the issues are custom based on policy notifications not working properly. If you encounter any issues at all, please do send the details to Support and we will be glad to assist.

 

Email.png

 

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

KA413796 - After upgrading BPPM from 9.0 to 9.5, all users are seeing a blank operations console when logging in.

KA412943 - msend process is automatically terminated even if started with "-p MpServerIdleTimeout=0"

KA412821 - How to limit the number of BPPM 9.5 Admin consoles that can run at once.

KA413160 - IIWS 9.5 installer shows version details as 9.0 on the installer screen

KA412682 - Are the BPPM Best Practice Webinar details available?

KA414162 - With BPPM 9.5, the ProactiveNet.log contains KM_VERSION and PRODUCT_VERSION DO NOT MATCH messages.

KA414317 - Install of 9.0 SP3 Integration Service (IS) deleted the cell directories..

KA414526 - BPPM CMDB Extensions install - BPPM_CDM_Extensions-OSD.out shows ERROR 120014 for State attribute.

KA414606 - After upgrading from BPPM 9.0 to BPPM 9.5, some LDAP users get a 'Navigation Pane Options Error' when logging into the ops console.

 

Popular Knowledge Articles

KA361528 -Supported Oracle database versions for use with the BMC ProactiveNet Performance Management (BPPM) Server

KA359011 - How to configure/troubleshoot LDAP authentication in BPPM.

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

KA347733 - User name (PNUSER) and password (PNPASS) environment variables are not set - in this mode only minimal commands are allowed" is seen when issuing pw commands. 

KA361960 - Is there a way to remove stale auto-discovered devices from BPPM ?

 

“In the Know”…Do you know?

 

Do you use Chat to get quick answers to product questions? If not, check it out as this is another channel of support available to customers. Join us for a quick chat and we’ll get you started on resolving your concerns. Learn more about Chat

 

Have you heard of the AMIGO program? Looking to upgrade in the near future? Get on board with AMIGO and we’ll help you plan your upgrade to ensure a smooth transition to the next version of the products you are using.

 

Don’t forget our Webinars! Check out the details here: BMC ProactiveNet Performance Management (BPPM) 9.5 Best Practices Webinar Series

 

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

 

 

Feedback1.jpg

 

Help us determine how we are doing. Use the rating system at the bottom of this blog to rate this post!

Share:|

Managing users with LDAP and Microsoft Active Directory within BPPM is easy and quick to integrate. It provides users even more authentication security and helps BPPM easily integrate with the existing user setup. After all is said and done, what we see most often in Support…. is the failure of Active Directory to authenticate the BPPM user


So let’s take a quick look at the basics of configuration and then we’ll look at some of the more common errors and issues.

 

Basic LDAP and Active Directory configuration

 

The Basic LDAP and Active Directory configuration details are listed in our documentation starting on page 1607 of http://documents.bmc.com/supportu/documents/97/40/449740/449740.pdf.

 

Here are a few details worth noting about Active Directory use

 

Basic group configuration for LDAP and Active Directory
Every user must belong to a group which maps to the groups in BMC ProactiveNet Server. Groups assign the user’s roles and responsibilities to each other. That is, the external authentication system must be able to identify and authenticate the user but must also be able to identify which group that user belongs to. Following methods ensure proper functionality and identification between systems:
•    Add the BMC ProactiveNet Server groups to your LDAP system
This method allows to take the desired BMC ProactiveNet Server groups and create them in your LDAP or Active Directory system. You must ensure that the users that you want to allow to log in, are members of those groups.
•    Add the LDAP groups to your BMC ProactiveNet Server
This method allows to create the desired LDAP or Active Directory groups and create them in the BMC ProactiveNet Server.
Warning: All group names are case sensitive. You must spell and ensure the correct case of the group names while implementing any of the methods.

 

Worth Noting:
•    Port 389 is used by Active Directory. An LDAP server port can also be accessible from the BMC ProactiveNet Server. If you use an LDAP integration, port 389 can be accessed from the BMC ProactiveNet Server (from the server to the Active Directory port).
•    Kerberos authentication to Active Directory is not currently supported.
•    Siteminder authentication is not currently supported


What info does Support need to troubleshoot Active Directory problems?


While the type of information will vary depending on platform and customer environment. We will always ask for the following:

We will ask for FINEST level debug. So please change the level of default logging details in the pw\pronto\conf\ias_logging.properties file
From:
    java.util.logging.FileHandler.level=FINE
    com.bmc.sms.ixscomm.level=INFO
To:
    java.util.logging.FileHandler.level=FINEST
    com.bmc.sms.ixscomm.level=FINEST
Restart JServer
    pw process restart jserver

 

Login using an LDAP username so we can detect something in the logs.
Then send to Support the following logs:
1) From pw\pronto\logs\ias\
    ias0.log
2) From pw\pronto\conf\
    ias.properties
    ldap_configuration.xml
    ldap_configuration_query.xml
    ldap_ppm_group_mapping.xml
We may need more details but the majority of issues seen will require the details and files referenced above.


Common Active Directory Issues and topics:

 

How to configure/troubleshoot LDAP authentication in BPPM


Unable to validate user when using LDAP user to login BPPM console

 

If you are seeing the following error: "failed to create DirContext for LDAP server HOST.DOMAIN.COM due to javax.naming.CommunicationException: HOST.DOMAIN.COM:389 [Root exception is java.net.ConnectException: Connection timed out: connect]. Please check your LDAP configuration." You will want to check out this link: Logging into BPPM via LDAP sometimes work, yet other times fails. There is no consistent reasoning for when it works or fails

 

Unable to log into Proactivenet Admin or Operations Console, and getting the error "BMC-BSW000002E User admin cannot be logged in: java.lang.NoClassDefFoundError:"

 

How to configure IAS “ldap_configuration.xml” in order to use more than one search condition in the <groupSearchFilter>

BPPM integration with LDAP is not working. Error failed to retrieve groups from LDAP server..InvalidSearchFilterException: Missing 'equals';?

 

What is the correct syntax for the 'Group Search Filter' when configuring LDAP for BPPM?

 

What can I do if I want to query several Active Directory groups? Can this be configured? For example: I want to include all Active Directory Groups which start with ‘BPPM_*’

 

If you have several LDAP user groups to query, the format used is comma separate list by using "com.bmc.sms.ixs.search.ldap.group" in ias.properties file.  For example, if you have LdapGroup1, LdapGroup2, LdapGroup3,groups configured on LDAP and you want only the user "username" to be validated against LdapGroup1 and LdapGroup2 then the ias.properties file should have the entry for example:

com.bmc.sms.ixs.search.ldap.group=LdapGroup1,LdapGroup2

 

How do you configure Active Directory?

 

Here are the basics in terms of the procedure to configure Active Directory with BPPM. Please see the full documentation here: http://documents.bmc.com/supportu/documents/97/40/449740/449740.pdf

 

Please take note that some of some of this configuration can be done via ops console (options > administration tab > scroll to bottom and select integrations). The gui updates the ldap_configuration.xml and ias.properties, but the map file would need to be manually edited.

 

1. Access the /pw/pronto/conf folder.

2. Edit the ias.properties file, update the following entry to TRUE and save the file. com.bmc.sms.ixs.enable.ldap.login=true. This will enable you to log into LDAP if you are a LDAP user.

3. Open the ldap_configuration.xml file using a text editor and  Configure a LDAP server host by adding the following lines for example, before the </ldapList> tag

<ldap alias="test">

<host>adserver.acme.com</host>

<port>389</port>

<version>3</version>

<baseDN>DC=activedir,DC=acme,DC=com</baseDN>

<connectionUserName>userid@activedir.acme.com</connectionUserName>

<connectionPassword encrypted="false">password</connectionPassword>      <userIdAttribute>sAMAccountName</userIdAttribute>

<useSSL>false</useSSL>

<groupMemberAttribute>member</groupMemberAttribute>    memberOfAttribute>memberOf</memberOfAttribute>  <userSearchFilter>(objectClass=organizationalPerson)</userSearchFilter>

<groupSearchFilter/>

</ldap>

and save the ldap_configuration.xml file

4. Open the ldap_ppm_group_mapping.xml file using a text editor and create a map between LDAP groups and BMC ProactiveNet Performance Management (PPM) groups.

For example, if you have a LDAP group called MyLdapGroup and you need to map it against a PPM group called "Full Access" then the ldap_ppm_group_mappings.xml file should have an entry for example,

<entry key="MyLdapGroup">Full Access</entry>

You can find out the group membership of the ldap user using the command

 

net user ldapuser /DOMAIN

e.g.

net user nmadmin /DOMAIN

5. Enter the comma separated list of LDAP groups that you need to authenticate the user against in the ias.properties file. The property used to store this value is com.bmc.sms.ixs.search.ldap.group in the ias.properties file.

For example, if you have LdapGroup1, LdapGroup2, LdapGroup3, LdapGroup4 groups configured on LDAP and you want only the user "username" to be validated against LdapGroup1 and LdapGroup2 then the ias.properties file should have the entry for example,

com.bmc.sms.ixs.search.ldap.group=LdapGroup1,LdapGroup2

6. Check whether the property com.bmc.sms.ixs.default.group.present.check is set to false in the ias.properties file. By default this property is set to false. If this property is set to true, create a separate group for the corresponding LDAP group in the PPM environment.


BleedingHeart.jpgHave you updated BPPM 9.5 to address the Heartbleed Vulnerability?BleedingHeart.jpg

 

BPPM 9.5 was impacted by the Heart Bleed vulnerability. Please note that this security concern only exists in BPPM 9.5. All other versions of BPPM are not affected as they are using older versions of OpenSSL. BPPM 9.5 runs with Open SSL 1.0.1c and so it IS vulnerable. We have generated patches for each of our supported platforms and the patches can be downloaded from our FTP site under the following location:

 

ftp.bmc.com/pub/BPPM/PATCHES/9.5/HeartBleed_Patch/Apache-Linux_Hotfix_for_HeartBleed_Issue.zip

ftp.bmc.com/pub/BPPM/PATCHES/9.5/HeartBleed_Patch/Apache-Solaris_Hotfix_for_HeartBleed_Issue.zip

ftp.bmc.com/pub/BPPM/PATCHES/9.5/HeartBleed_Patch/Apache-Windows_Hotfix_for_HeartBleed_Issue.zip

ftp.bmc.com/pub/BPPM/PATCHES/9.5/HeartBleed_Patch/readme_BPPM_OpenSSL_Heartbleed_fix_PS.txt

 

 

 

Computer.png

 

 

 

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

 

 

KA412547 - With a 9.5 cell, a slot modification is not being back propagated.

KA412560 - Running 'pw dbconfig set' results in problems connecting to the database.

KA412861 - All events from PATROL Agent to BPPM cell show "Incoming event information could not be parsed".

KA413355 - A 'pw sys status' or 'pw p l' on Solaris/Linux show both mcell and acell to be not running even though they are.

KA413360 - BPPM 9.5 installation on Windows 2012 cluster is failing on Secondary Node with "Unable to validate custom cluster name".

 

Popular Knowledge Articles

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

KA314023 - Diagnosing problems with ProactiveNet Integration with PATROL.

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

KA307241 - How to enable trace for IBRSD?

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


“In the Know”…Do you know?

 

Have you joined our Customer Support Community yet? If not, head on over to the link and learn how you can help us by providing feedback to enhance your Customer Support experience.

 

Do you use Chat to get quick answers to product questions? If not, check it out as this is another channel of support available to customers. Join us for a quick chat and we’ll get you started on resolving your concerns. Learn more about Chat

 

Have you heard of the AMIGO program? Looking to upgrade in the near future? Get on board with AMIGO and we’ll help you plan your upgrade to ensure a smooth transition to the next version of the products you are using.

 

Don’t forget our Webinars! Check out the details here: BMC ProactiveNet Performance Management (BPPM) 9.5 Best Practices Webinar Series

 

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

 

Feedback1.jpg

 

Help us determine how we are doing. Use the rating system at the bottom of this blog to rate this post!

 

 



Share:|

Is it possible to migrate our existing from PATROL 7 thresholds to BPPM 9.5 Central Monitoring Administration (CMA)? This is a question which has come up recently so I thought it would be good to address it in our Community.

 

For example, here is a question we have received a few times over the last month. Is there an Utility available to transfer or migrate our “/AS/EVENTSPRING/PARAM_SETTINGS/THRESHOLDS" Variables in the new BPPM 9.5 environment?

 

Unfortunately, we do not have a method for exporting the PATROL 3.x or 7.x thresholds and importing them into BPPM through the CMA.  With BPPM 9.5 and a Patrol Agent 9.5 the threshold configuration can be automatically updated on the BPPM server by configuring a server threshold Policy in CMA. With CMA, you would configure a global policy with tags to allow the Patrol Agent 9.5.00, after restart, to connect to the Integration Service which would have the same tag configured as in the policy; the thresholds are then updated in the BPPM Server for the associated monitors.

 

We have some utilities and scripts with previous versions of BPPM which can import thresholds into the BPPM Server but this cannot be done in CMA. Also, these scripts will not allow you to configure baselines, intelligent thresholds, or blackout time frame available only in BPPM and not in Patrol.

 

With CMA you can automatically update thresholds on both the Patrol configuration and the BPPM server but that requires configuring policies. So therefore it facilitates configuration of monitors, thresholds, blackout on both Patrol and BPPM from a central point. However, we do not have a clear migration option for moving the Patrol thresholds into BPPM. If this is of interest, we recommend opening an Idea in our Communities, to let us know the use case you wish to see implemented.

 

Here’s another reference to thresholds and PATROL KA355723 (details below)

Problem

PATROL Agent has __tuning__ parameters set to adjust the thresholds on various parameters. However, in ProactiveNet there is no signature or absolute thresholds set. Is this by design or is there a missing step that should sync the PATROL/ProactiveNet thresholds?

 

Solution

With regard to the parameters set in PATROL; these do not come over to ProactiveNet. Basically all PATROL does is forward parameter values to the Integration Service. There is no threshold information sent. This is by design.

 

If you want threshold information configured then this has to be done separately though BPPM. BPPM already has a number of default thresholds configured along with building up a picture over time of what is normal for the environment and alerting if things fall outside of the "norm". You can manually specify additional thresholds or adjust the ones already configured, or it is possible to import thresholds from Patrol Agents in to BPPM. This involves running the following command:

 

pw adapter -type patrol -get_thresholds c:\thresholds.txt -i -v -pproxy_host <hostname/IP address> -pproxy_user <username, default is admin> -pproxy_passwd <password, default it admin> (if you're using a different port other than the default you will need to specify this as well)

 

The Patrol Agent keeps track of default thresholds and overrides. Default thresholds are classified as "GLOBAL THRESHOLDS". Overrides are classified as "INSTANCE LEVEL THRESHOLDS".

 

This will export the thresholds to the file specified. You can then run the following command to import them into BPPM:

 

pw threshold loadpatrolthreshold <filename withpath> [-v]

 

General CMA Guidelines with regard to PATROL

Let’s take a look at some of the guidelines for working with CMA regarding monitoring solutions and PATROL.

 

If a monitoring solution is configured through a policy in Central Monitoring Administration, do not modify the configuration through a BMC PATROL tool, such as PATROL Configuration Manager or the pconfig commands. Modified configuration can be overwritten with the next policy update.

 

 

If your environment includes a BMC PATROL Agent that manages monitoring solutions configured through Central Monitoring Administration and configured through BMC PATROL tools, you have the following options:

 

(Recommended) Use a different BMC PATROL Agent for the different kinds of monitoring solutions. Use PATROL Configuration Manager or other PATROL consoles to manage the non-Central Monitoring Administration monitoring solutions.

(Recommended) If the latest release of the Central Monitoring Repository includes an updated monitoring solution that works with Central Monitoring Administration, upgrade the monitoring solution.

•(Not Recommended) Manage the BMC PATROL Agent with PATROL Configuration Manager instead of Central Monitoring Administration.

 

Central Monitoring Administration does not completely replace all functionality available in PATROL Configuration Manager or PATROL Consoles. Use PATROL Configuration Manager or PATROL Consoles in the following situations:

 

 

•If you did not set the Central Monitoring tag on the BMC PATROL Agent through the installation package or BMC Server Automation, then use PATROL Configuration Manager or the pconfig command.

•Administer monitoring solutions which cannot be configured through Central Monitoring Administration.

•Perform BMC PATROL Agent operations such as restart, purge, and kill.

•Access menu commands, BMC PATROL Agent thresholds, and recovery actions.

•Filter metrics that are collected on the BMC PATROL Agent, blackout, and PATROL thresholds.

 

Considerations for BMC PATROL Agent and monitoring solution deployment

The following list presents considerations and guidelines for configuring the BMC PATROL Agent and monitoring solution deployment.

•    Leverage distribution software, such as BMC (BladeLogic) Server Automation, to deploy the monitoring solution packages. With BMC ProactiveNet integration with BMC Server Automation, you can deploy BMC PATROL Agents and monitoring solutions with relevant configuration information, including the Central Monitoring Administration tag and the BMC PATROL Agent location. For details about BMC Server Automation integration with BMC ProactiveNet, see BMC ProactiveNet User Guide.

•    Specify the Central Monitoring Administration tag when you create a monitoring package (for details, see Creating and editing component installation packages), or specify the tag through the BMC BladeLogic Console. You can also use the BMC PATROL Agent pconfig command or PATROL Configuration Manager to set the tag, but if the recommendations are followed then those tools would not be necessary.

•    Monitoring solutions must expose the relevant metadata and conform to development guidelines to Central Monitoring Administration for configuration.

o    For a list of enabled monitoring solutions, see Monitoring solutions configurable through Central Monitoring Administration.

o    To create a custom monitoring solution, see Building a PATROL Knowledge Module Developers Guide from the BMC Support website.

•    If you delete a monitoring policy, manually restart the BMC PATROL Agent. For example, if a BMC PATROL Agent has monitoring policies for OS and database, and you later decide to remove the OS, you need to restart the BMC PATROL Agent.

For details, see the BMC PATROL Agent Reference Manual from the BMC Support website.

 

To restart the BMC PATROL Agent using BMC PATROL Configuration Manager

1.    In PATROL Configuration Manager, select the agent.

2.    From the Tools menu, select Reinitialize Agent.

3.    To restart the BMC PATROL Agent using a pconfigcommand

               In a command window, run the pconfig +RESTART command with the following syntax:

                              pconfig +RESTART [+verbose] [-port <portNumber>] [-host <hostName>] [-timeout <timeoutValue>]

Warning

If a BMC PATROL Agent is already configured through the PATROL Configuration Manager or through the Tools > Configure options in the BMC ProactiveNet Administration Console, and the agent is integrated with BMC ProactiveNet through the adapter for BMC PATROL, do not add a tag to that BMC PATROL Agent. Instead, continue managing the configuration for that BMC PATROL Agent through the PATROL Configuration Manager.

If you add a tag to the BMC PATROL Agent, configuration information might be overwritten. Duplicate instances will be created, conflicting monitor instances that were synchronized through PATROL Configuration Manager will be marked for deletion, and all historical data will be lost.

 

Monitoring policy configuration guidelines

 

Use the following guidelines and recommendations to configure monitoring policies in Central Monitoring Administration. For configuration details, see Creating or editing a monitoring policy.

•    Avoid assigning the same tag to several different policies. Too many policies with the same tag make it difficult to determine the final configuration.

•    Consider the following performance factors when you configure monitoring policies:

o    Avoid policies that set thresholds for a large number of instances that are discovered by using regular expressions. If the threshold applies to all instances, BMC recommends using the global thresholds settings that are available through the BMC ProactiveNet Operations Console. Proliferation of instance thresholds could adversely affect the performance of the BMC ProactiveNet Child Servers.

o    Plan policy edits. Editing policies triggers a push of configuration on all the agents and the BMC ProactiveNet Child Servers (for server-side actions). For large environments, plan edits for policies in advance, and group together all the required changes rather than editing the policies multiple times for minor changes.

o    Combine all the actions for a specific tag in a single policy. Edits are more efficient and the final configuration is less confusing.

o    For BMC PATROL Agents with agent-level thresholds, which are set only from the BMC PATROL Console, do not set thresholds through monitoring policies to avoid duplication of processing.

•    Use the Copy baseline from device for environments that use VMs that are expected to have similar configuration with regards to the CPU, memory, and installed applications.

•    For the same monitor type with different versions of the monitoring solution, use the following guidelines:

o    If different versions have the same configuration settings, then use the latest version of the monitoring solution to configure the policies.

o    If different versions have different configuration settings, then create separate policies and separate tags for the different versions.

 

Performance considerations

 

The following list presents performance considerations for Central Monitoring Administration.

•    BMC ProactiveNet Central Server.

o    Do not monitor directly from the BMC ProactiveNet Central Server. Perform all monitoring from the BMC ProactiveNet Child Servers.

o    For performance considerations related to policies, see Monitoring policy configuration guidelines.

•    BMC ProactiveNet Child Servers. From the perspective of Central Monitoring Administration, the impact on the BMC ProactiveNet Child Servers is a function of the threshold configurations and the server-side actions. The guidelines given for configuration of the policies would ensure that the impact on the BMC ProactiveNet Child Servers is minimal.

•    Integration Services. Integration Services push configuration information to the BMC PATROL Agents. As long as the Integration Service is sized to handle the load of the data collection, no additional considerations are necessary from a Central Monitoring Administration perspective.

 

Security considerations

The information in this section is specific to Central Monitoring Administration. A list of ports required for data collection and other configuration is available the BMC ProactiveNet Installation and Configuration Guide.

•    Firewall Considerations.

o    Port 3183 (default) is required for communication between the BMC ProactiveNet Central Server and the Integration Services distributed across the environment. The connection is initiated by the Central Server.

o    Port 8093 (default) is required for communication between BMC ProactiveNet Child Servers and Central Monitoring Administration. The connection is initiated by the BMC ProactiveNet Child Server.

o    Certain actions, such as registration of the BMC ProactiveNet Child Servers and using the REST Web Services, require access to web services on the Central Server. Port 80 or 443 needs to be accessible on the Central Server from the BMC ProactiveNet Child Servers or the client machines invoking the APIs.

•    Access Control. Central Monitoring Administration is only accessible to users who are assigned the Access to Central Admin permission. After permission is available to the user, the user can create policies which impact any of the objects in the entire deployment. Only give this permission to "Super Admin" users to limit the exposure to a minimal set of users. For details, see Granting user access to Central Monitoring Administration.

 

For other upgrade/migration concerns, please visit our link to the BPPM 9.5 Upgrade & Migration Best Practices Webinar https://communities.bmc.com/docs/DOC-30645#

 

BleedingHeart.jpgUPDATE: Heart Bleed Bug patches available for BPPM 9.5 

BPPM 9.5 was impacted by the Heart Bleed vulnerability. Please note that this security concern only exists in BPPM 9.5. All other versions of BPPM are not affected as they are using older versions of OpenSSL. BPPM 9.5 runs with Open SSL 1.0.1c and so it IS vulnerable. We have generated patches for each of our supported platforms and the patches can be downloaded from our FTP site under the following location:

ftp.bmc.com/pub/BPPM/PATCHES/9.5/HeartBleed_Patch/Apache-Linux_Hotfix_for_HeartBleed_Issue.zip

ftp.bmc.com/pub/BPPM/PATCHES/9.5/HeartBleed_Patch/Apache-Solaris_Hotfix_for_HeartBleed_Issue.zip

ftp.bmc.com/pub/BPPM/PATCHES/9.5/HeartBleed_Patch/Apache-Windows_Hotfix_for_HeartBleed_Issue.zip

ftp.bmc.com/pub/BPPM/PATCHES/9.5/HeartBleed_Patch/readme_BPPM_OpenSSL_Heartbleed_fix_PS.txt

 

Computer.png

 

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

KA411445 - A blackout policy with a 9.5 cell is not working as expected. 

KA411569 - With a 9.5 cell, events do not have mc_smc_alias and mc_smc_id slots automatically set and therefore not impacting any CI.

KA410273 - Changing and viewing thresholds in BPPM 9.5.

KA410156 – Is it possible to generate an event from an email?

KA410341 - Does BPPM 9.5 support Oracle 10.2.0.4 for the database installation?

KA410263 - Does BPPM 9.5 support multiple Oracle schemas in the same Oracle database?

KA410769 - BPPM Custom folders on Operator Console have a limit of 500 CI's. Can this number be increased?

KA410965 - How can I have the hostname included in the msg slot for MC_CELL_HEARTBEAT_FAILURE event for a patrolagent ?

KA411694 - Is BMC ProactiveNet Performance Management (BPPM) vulnerable to the OpenSSL 'Heartbleed' (CVE-2014-0160) bug?

 

 

Popular Knowledge Articles

KA356813 - How to check the default retention period of raw/condensed/baseline/event data and how to reset them.

KA350205 - Publishing fails in Impact Model Designer with Failure Message: ERROR-9940   

KA356062 - How to delete a device that is auto-discovered by PATROL Adapter in BPPM?

KA348029 - How to view the remote cells in the ProactiveNet operation console?  

KA363486 - How to customize local actions in BPPM?

 


“In the Know”…Do you know?

 

Have you joined our Customer Support Community yet? If not, head on over to the link and learn how you can help us by providing feedback to enhance your Customer Support experience.


Do you use Chat to get quick answers to product questions? If not, check it out as this is another channel of support available to customers. Join us for a quick chat and we’ll get you started on resolving your concerns. Learn more about Chat


Have you heard of the AMIGO program? Looking to upgrade in the near future? Get on board with AMIGO and we’ll help you plan your upgrade to ensure a smooth transition to the next version of the products you are using.


We have our Intelligent Ticketing Community space available now! You can also access Intelligent Ticketing documentation here

.
Don’t forget our Webinars! Check out the details here: BMC ProactiveNet Performance Management (BPPM) 9.5 Best Practices Webinar Series


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

 

Feedback1.jpg

 

 

   Help us determine how we are doing. Use the rating system at the bottom of this blog to rate this post!

Share:|

We are using monitoring tools to monitor our servers, but what monitors the monitoring tool? The answer is simple with BPPM. BPPM has its own built in self-monitoring.

 

The BMC ProactiveNet Self-monitoring Service (also known as the local agent) is a local service dedicated to monitoring the health of the BMC ProactiveNet Server. This will help ensure that the BMC ProactiveNet Server runs at peak performance. The Self-Monitoring Service, which is automatically installed on the BMC ProactiveNet Server, collects metrics about only the BMC ProactiveNet Server performance.

 

When you install the BMC ProactiveNet Server, several out-of-the-box processes are created and monitored by default. These processes include the Apache server, the database installed, and the monitors corresponding to the operating system, and so on. This type of default monitoring is called self-monitoring.

 

 

NOTE:

Due to conflicts with the BMC ProactiveNet Server and the drain on the resources of the BMC ProactiveNet Self-Monitoring Service, BMC Software does not recommend enabling the BMC ProactiveNet Integration Service on the same computer where the BMC ProactiveNet Server is installed. BMC does not recommend using the BMC ProactiveNet Self-Monitoring Service for monitoring anything other than the BMC ProactiveNet Server.

Also, take note, that when you upgrade to a later version of BMC ProactiveNet Server, these monitors continue to exist. However, if you have deleted these monitors in the earlier version, they are not recreated.

 

The following is a list of self-monitored processes:

PnAgent - The BMC ProactiveNet Agent running on the server

PwTray (only in Microsoft Windows)- The tray process, which indicates the status of the BMC ProactiveNet

Server

acell - The administrative cell

dbsrv - The Sybase SQL Anywhere server process

httpd - The Apache server process

jserver - The main BMC ProactiveNet Server process

mcell - The master cell, which processes the events in the BMC ProactiveNet Server

pronet_cntl - The agent controller process, which communicates with the remote Agent/Integration

Server systems

rate - Processes the collected data services

tunnelproxy - The process, which allows connection to the agent, behind a firewall Windows System, Linux System, or Solaris System

Web URL – Refers to the IP of the device. The Web URL process monitors the default page of the BMC

ProactiveNet web console.

ProactiveNet Agent Status - Refers to the monitoring of the local ProactiveNet Agent. The ProactiveNet Agent Status indicates whether the server was able to communicate with the ProactiveNet Agent or not.

Database related monitors such as Sybase query and Sybase Intelliscope monitor the health of the BMC ProactiveNet Server back-end databases. For BMC ProactiveNet Server with Oracle as the back-end database, Oracle Query and Oracle Intelliscope monitors are used.

 

Here is the Solaris specific setting for the JRE BMC ProactiveNet Self-monitoring Service - Solaris Edition

SelfMonitoringServiceonSolaris.jpg

 

Here is the Windows specific setting for the JRE BMC ProactiveNet Self-monitoring Service – Windows Edition

 

SelfmonitoringServiceonWindows.jpg

 

How do I enable debug for Self-Monitoring?
If you run pw debug list-a ProactiveNet_Server_hostName_or_IPaddress in BPPM 9.5, it lists the status of all visible subsystems being run by the BMC ProactiveNet Self-monitoring Service on the BMC ProactiveNet Server. This information can then be used for setting debug levels on individual processes and visible subsystems on the BMC ProactiveNet Server or any Integration Service.

 

The following pw debug commands are available:
pw debug file
pw debug list
pw debug on|off

 

Do I need to install the Monitor the Monitor KM on Integration Service hosts?

The Monitor the Monitor KM is not needed on Integration Service 9.5 hosts and it will not monitor the Integration Service processes. The KM was designed for the older Integration Service processes. In-built self-monitoring replaces the KM in version 9.5. You must also install a PATROL Agent and an OS KM on the Integration Service nodes so that you can monitor the Integration Service processes externally.

 

How do I check on the health of the BMC ProactiveNet components?

BMC ProactiveNet displays the health of the following components in the ProactiveNet Health node of the BMC

ProactiveNet Operations Console:

BMC ProactiveNet Cell

BMC ProactiveNet Integration Service

BMC PATROL Agent

BMC ProactiveNet Central Server and Child Server In the navigation tree of the Operations Console, click Global > Event Collectors to view the ProactiveNet Health node.

 

The following figure shows the ProactiveNet Health node as it appears in the Operations Console.

HealthCheckBPPM.png

 

You can use the different notebooks to see the details regarding the health status events displayed in the Operations Console.  For example: The Details notebook displays detailed information about the system for which the event was generated. Such events as classified as self-monitoring events and are displayed as such in the Summary notebook as shown below:

Notebooks.png

When you use Self-Monitoring you would need to be sure that if you  have changed the database configuration by using the pw dbconfig set command, then ensure that you use the new credentials to edit the database related self-monitoring processes such as Sybase Query, Oracle Query, Sybase Intelliscope, and Oracle Intelliscope.

 

What do I do if I want to monitor BMC ProactiveNet Server Components externally?
PATROL for BMC ProactiveNet Self-Monitoring product provides a Knowledge Module (KM) that helps you discover instances, collect performance metrics and thereby monitor the BMC ProactiveNet Server and the BMC ProactiveNet Integration Service along with their associated components. The BMC Monitor the Monitor KM can be used if external monitoring of ProactiveNet components is needed.

It can monitor BPPM, IS and its components as well. Refer the Self-monitoring guide for more details:
https://docs.bmc.com/docs/display/public/MTM11/Home

 

The basic overview of the “Monitor the Monitor” or PATROL for BMC ProactiveNet Self-Monitoring KM is as follows:

 

Operating system (OS) level monitoring: This product provides an OS level monitoring of the BMC ProactiveNet Server and the BMC ProactiveNet Integration Service. It helps you monitor the health of OS entities such as file system resources, memory resources, and the processor. The BPPM_MTM application class parameters provide OS level monitoring.

 

Component monitoring: This product provides component level monitoring of some critical processes related to the BMC ProactiveNet Server and the Integration Service. The BPPM_MTM_COMPONENT application class parameters provide component level monitoring.

 

Status monitoring and data collection: This product provides monitoring of the PATROL Agents connected to the Integration Services that are being monitored. It monitors metrics such as the number of PATROL Agents connected (or disconnected) to the Integration Service, the data collection and connection status of the PATROL

Agents associated with the Integration Service, and so on. The BPPM_MTM_CONNECTION_PROFILE application class parameters provide status monitoring.

 

Failover configuration: This product provides you with the capability of handling failover for Integration Services operating in a failover environment. With this, the product accounts for PATROL Agent failover to a different Integration Service.

 

Email notification configuration: This product helps you configure email notification for all the parameters available with version 1.1.00 of the product. With this, if a parameter goes into an alarm state, an email notification is sent to the designated email ID with detailed information about the alert.

 

NOTE: If you are running a version prior to 9.5, you can use the Monitor the Monitor KM but 9.5 forward does not require it.

 

The BMC Monitor the Monitor KM does not discover and monitor the 9.5 Integration Service and must not be used with the 9.5 Integration Service. Built-in self-monitoring is significantly enhanced in version 9.5 and the BMC Monitor the Monitor KM is no longer needed. However, BMC recommends that you use the PATROL Agent and operating system KMs for additional self-monitoring. Built-in self-monitoring replaces the KM in version 9.5. You must also install a PATROL Agent and an OS KM on the Integration Service nodes so that you can monitor the Integration Service processes externally.

 

 

 

Computer.png

 

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

KA403507 - BPPM is generating large hprof files in the pw\pronto\logs directory.

KA408342 - BPPM CMDB extensions install is hanging at step CDM-Extensions.

KA409463 - BPPM 9.5 instance hierarchy is showing the PATROL Agent and KM for a device. This is different behaviour to BPPM 9.0

KA410247 - BPPM 9.5 - Time of events in event view are 1 hour ahead of when they actually occurred.

KA410356 - When configuring Atrium CMDB in the operations console or with integrate_atrium_cmdb script, connection to UDDI fails if UDDI is configured for https

KA410757 - With BPPM 9.5, is it possible to use the IS on the central server as a staging IS?

KA410773 - The mcell-log shows undefined class messages for BMC_SI_CI_PATTERN and BMC_SI_REL_PATTERN.

KA410795 - After an upgrade from SIM to BPPM, it is not possible to create/delete/edit a CI or impact relationship in IMD.

 

 

Popular Knowledge Articles

KA308615 - How to configure ProactiveNet integration with BMC PatrolAgent using PATROL Proxy Server?

KA321519 - Network Ports used with and for Proactivenet   

KA374546 - Old mcdb files are not being automatically deleted by statbld which can result in a full filesystem.

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

KA366333 -BMC ProactiveNet Event Adapters is not running properly as a service.  The service starts, but no events are received, and task manager does not show any perl.exe nor msend.exe processes for the adapters.

 

 

“In the Know”…Do you know?

 

Have you joined our Customer Support Community yet? If not, head on over to the link and learn how you can help us by providing feedback to enhance your Customer Support experience.

 

 

Do you use Chat to get quick answers to product questions? If not, check it out as this is another channel of support available to customers. Join us for a quick chat and we’ll get you started on resolving your concerns. Learn more about Chat

 

Have you heard of the AMIGO program? Looking to upgrade in the near future? Get on board with AMIGO and we’ll help you plan your upgrade to ensure a smooth transition to the next version of the products you are using.

 

We have our Intelligent Ticketing Community space available now! You can also access Intelligent Ticketing documentation here.

 

Don’t forget our Webinars! Check out the details here: BMC ProactiveNet Performance Management (BPPM) 9.5 Best Practices Webinar Series

 

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

 

Feedback1.jpg

 

 

Tell us how we are doing. Use the rating system at the bottom of this blog to rate this post! Comments and feedback are welcome!

Share:|

If you have BPPM 9.x you have access to the Central Monitoring Administration which allows you to manage BMC PATROL configuration across one or more BMC ProactiveNet Child Servers

 

The diagram below illustrates a multiple BPPM Server environment with a Central BPPM Server with the Central Management and Administration (CMA) module and Child Servers.

 

 

 

    CMAArchitecture.jpg

BMC Recommends implementing one of two architectures for CMA.  The two options are listed below with their pros and cons.

 

Option One - Implement a single CMA Instance for all environments including Development, Test and Production.

Pros

1)    The creation, testing, and deployment of monitoring policies into production are very easy because you do not have to copy or export/import any data.  The application of policies to Development, Test and Production is simply managed in the policy’s agent selection criteria.

 

2)    It requires less infrastructure nodes and components.  Only a single Staging Integration Service host is needed.  Only a single CMA instance is used.

Cons

1)    This many not be supported in some sites where all the necessary connections between Development, Test and Production environments are not available or allowed to be connected over the network.

 

2)    Due to the powerful ease of use, it is easier for administrators to make mistakes applying policies unintentionally to production.  However, this can be managed.

 

Option Two - Implement a separate CMA Instance for the Development, Test and Production environments each.

Pros

1)    Is supported in sites where all the necessary connections between Development, Test and Production environments are not available or allowed to be connected over the network.

 

2)    Provides a platform and supports policy management methods that help prevent administrators from making mistakes when applying policies to production.

Cons

1)    The creation, testing, and deployment of monitoring policies into production require more manual effort because you have to export/import policy data from Development to Test and from Test to Production.

 

2)    Policies could get out of synch across the Development, Test, and Production environments if not managed properly.  Keeping them up to date is more of a manual process supported by the export/import utility.

 

3)    It requires more infrastructure nodes and components.  The Development, Test, and Production environments should each have a dedicated Staging Integration Service host and a dedicated CMA instance.

 

IMPORTANT: Neither method supports seamless creation, testing, and production deployment of updates and deletion for existing policies.  Updates and deletion of existing policies that are already in production should be created, tested, and populated to production leveraging the policy export/import capability.  This topic is discussed in detail in the configuration best practices.

In all scenarios, CMA communicates thorough the agent controller process on the BPPM Server(s) to the Integration Service nodes.

 

These implementation architecture options are not installation options.  The CMA components are the same.  These two implementation architecture options are simply choices in how you install CMA instances and connect them to the various BPPM Servers.

Accessing Central Monitoring Administration

1.    Ensure that you have access to Central Monitoring Administration.

2.    In a supported browser, open http://serverHostName/admin.

The serverHostName variable is the name of the BMC ProactiveNet Central Server where Central Monitoring Administration is enabled.

3.    Log in to Central Monitoring Administration.

The default user name and password are admin

 

Once you have accessed the Central Monitoring Administration console, what can you do? Here’s a couple of topics of interest:

Setting an intelligent threshold using Central Monitoring Administration

Which monitoring solutions can be configured using BMC ProactiveNet Central Monitoring Administration

Create or Edit a monitoring policy

 

BMC ProactiveNet Central Monitoring Administration enhancements in BPPM 9.5 - BMC ProactiveNet Central Monitoring Administration is enhanced to perform the following tasks:

•Configuring Monitoring policies

•Configuring Staging policies

•Configuring Blackout policies

•Adding Integration Services to BMC ProactiveNet Server

•Creating Integration Service clusters

•Enabling Global thresholds

NOTE:

Connectivity between the Integration Service processes and the Central Management & Administration module (CMA) has been consolidated.  CMA now communicates with each Integration Service through the BPPM Server that the Integration Service is connected to.

The new Central Monitoring Administration features in version 9.5 do not work with the 9.0 versions of the Integration Service and the BMC PATROL Agent. For information about the compatibility between BMC ProactiveNet and the BMC PATROL Agent, see BMC ProactiveNet and BMC PATROL Agent compatibility

 

Central Monitoring Administration Q&A

When trying to register a child server on the central server, we encounter an error using the following command: pw cmadmin registerChildServer -ChildHost=mychildhostname -ChildPort=443 -ChildUser=user -ChildPasswd=password -ChildProtocol=https

The error: An Exception has occurred. Message: Unable to register BMC ProactiveNet Child server as the Child server or web services running on it is unreachable. How do we troubleshoot this?

Verify the configuration is correct on the BPPM servers as central or child (as required) manually as

https://docs.bmc.com/docs/display/public/proactivenet95/Configuring+the+BMC+ProactiveNet+Server+as+a+Central+Server+Router+or+a+BMC+ProactiveNet+Child+Server+manually

 

If the child server is still not visible in the CMA and/or central ops console then please do the following:

1) On both BPPM servers (child and central) enable jserver debug
pw debug on -p jserver
2) Re-run the failing pw cmadmin registerChildServer command
3) Turn off jserver debug
pw debug off -p jserver
4) Zip up and send us the following from both child and central servers:
pw/pronto/logs/ProactiveNet.log (if possible send the whole pw/pronto/logs directory)
pw/pronto/logs/Jserver*
pw/pronto/logs/debug/*
pw/custom/conf/*
5) Please also run the following on the CMA server and send us the output:
sqli "select * from SERVER_DETAILS"

 

Can you restart a PATROL Agent via the CMA?
PATROL agent restarts from CMA will be achieved by manually selecting an agent and triggering a restart on it using the Reinitialize Agent/Query Agent feature available in CMA 9.5

 

Is there a way to export CMA policies from one BPPM server to another BPPM server?
Starting in BPPM 9.0 SP1 we added a new feature to import PCM RuleSets, which allows importing existing PCM RuleSets to new Agents. We currently do not have a feature to export CMA policies from one server to another. We do have an Idea posted about this on BMC Communities web site. We urge you to visit the Idea and vote for it if you would like to see it in a future release.
https://communities.bmc.com/ideas/2166

 

Is it possible to change the option of the view in CMA? For example, can we set the option of physical view or logical view?

The view presented in CMA is a general List view. There is currently, no option available to change the views in the CMA console.  We encourage you to submit an Idea via our BMC Communities to request this feature/functionality.


BMC Ideas is a new way to provide enhancement requests within our growing BMC Communities. 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

 

Does CMA support instance level threshold management?

CMA does support instance level threshold management. Please refer to the document
https://docs.bmc.com/docs/display/public/proactivenet95/Configuring+a+server+threshold

 

How can I make sure that one policy is applied before another if there are different tags?

The BMC PATROL Agent sends a configuration request by passing its tag or tags to Central Monitoring Administration, via the Integration Service. Central Monitoring Administration evaluates policies that match the tags, determines the final configuration to be applied, and sends the configuration information back to the agent. Monitoring is based on the configuration information received by the agent.

 

The BMC PATROL Agent initiates a configuration request after certain events, such as agent installation, agent restart, or changing a tag on the agent. If no policy matches the tags associated with the agent, the agent does not receive configuration information. The agent does not begin monitoring until a matching policy is created.

 

If a policy is created or updated, changes are pushed from Central Monitoring Administration, via the Integration Service, to BMC PATROL Agents with matching tags.

 

Can a PATROL Agent be assigned multiple tags used to apply policies from the CMA?

Yes it is possible to assign multiple tags to a single agent. You would need to have several pconfig policies each with a different tag name to apply multiple polices for same agent.

An example would be as follows:

/AgentSetup/Identification/TagsTAG/<tag name1>

/AgentSetup/Identification/TagsTAG/<tag name2>

/AgentSetup/Identification/TagsTAG/<tag name3>

The value for these variables can be the description of policy/tag

 

Where can I learn more about CMA?

https://docs.bmc.com/docs/display/public/proactivenet95/BMC+ProactiveNet+Central+Monitoring+Administration

 

 


Computer.png


Newly Published Knowledge Articles - New Content has been added!

KA409225 - In BPPM, a Query Agent can display a list of common PSL commands to be executed. Is it possible to add more PSL commands to this list?

KA409228 – Install of BPPM 9.5 server hangs at step 'Started CMDB Integration...'

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

KA408948 - BPPM Reporting 9.0.x does not work with BPPM Server 9.5

KA409568 - Trying to update Threshold Override(s) on multiple devices fails with a System Error

KA409576 - "Unable to establish the database connection for Report User" when installing BPPM 9.5 with Oracle database

KA409573 - BPPM 9.5 installation with Oracle database ended with warnings due to ORA-00942 on sys.props$ table

 

Popular Knowledge Articles

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

KA345591 - BPPM Cell crashes when xact files grows rapidly.   

KA356575 - Usage of the PATROL Proxy command "pproxcli"

KA356684 - Executing SQL Queries against the BPPM Database

KA354768 - Unable to validate user when using LDAP user to login BPPM console

 

 

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

 

The Pulse blogs share the experience of BMC Customer Support on how to understand and best use particular product features.  You can read more about the goals of Pulse Blogs in About the Customer Support Community These blogs are posted in the individual product community, but as many community members have multiple BMC ProactiveNet products, this document provides a summary and links to these posts to make them easier to find.

 

Don’t forget our Webinars! Check out the details here: BMC ProactiveNet Performance Management (BPPM) 9.5 Best Practices Webinar Series

 

  Feedback1.jpg

 

 

Was this helpful?  Are there related topics I missed? Please add comments to share your experience.

Share:|

BPPM 9.5 is here!


We have been anxiously waiting for its release and we have confirmed that it is now available for download from our EPD site. Under licensed products search for BMC ProactiveNet Performance Management Suite and then select BMC Server Monitoring 9.5.00. You will find BMC ProactiveNet 9.5.00 and you can download the components needed for the installation/upgrade.

 

BMC Software has released version 9.5.00 of the BMC ProactiveNet Performance Management Suite. This space describes the components you have licensed and how you can access and download those components.


This release includes updates to the following component products:
•BMC Application Diagnostics 2.5.00
•BMC PATROL for Amazon Web Services 1.2.00
•BMC PATROL for Citrix XenServer 3.1.00
•BMC PATROL for Converged Infrastructure 1.2.00
•BMC PATROL for DB2 9.0.10
•BMC PATROL for Jboss 3.0.00
•BMC PATROL for Log Management 2.7.10
•BMC PATROL for Microsoft Exchange Servers 6.0.00
•BMC PATROL for Microsoft SQL Server 9.5.00
•BMC PATROL for Microsoft Windows 4.7.00
•BMC PATROL for Oracle WebLogic 3.0.00
•BMC PATROL for Real End User Experience Management 2.5.00
•BMC PATROL for Tomcat AS 3.0.00
•BMC PATROL for Unix and Linux 9.12.00
•BMC PATROL for VMware vSphere 4.0.00
•BMC ProactiveNet 9.5.00
•BMC Real End User Experience Monitoring and Analytics 2.5.00

 

Features and enhancements available in this release are detailed here: https://docs.bmc.com/docs/display/public/proactivenet95/9.5.00+enhancements


Here’s an overview of what you can see in BPPM 9.5:

 

Integration with the BMC PATROL Agent
•Reduction of footprint
•Reliable collection of data
•Self health monitoring
•Event integration
•Event with monitor association
•Streaming
•Reduction in the number of processes that were running

 

Configuring multiple BMC ProactiveNet Servers to connect to the same Oracle database - The procedure to install multiple BMC ProactiveNet Servers and connect them to use the same Oracle database is the same as that documented at Installing the BMC ProactiveNet Server on Microsoft Windows with Oracle as database or Installing BMC ProactiveNet on Linux or Solaris with Oracle as database depending on your operating system.

 

BMC ProactiveNet Central Monitoring Administration enhancements - BMC ProactiveNet Central Monitoring Administration is enhanced to perform the following tasks:
•Configuring Monitoring policies
•Configuring Staging policies
•Configuring Blackout policies
•Adding Integration Services to BMC ProactiveNet Server
•Creating Integration Service clusters
•Enabling Global thresholds
The new Central Monitoring Administration features in version 9.5 do not work with the 9.0 versions of the Integration Service and the BMC PATROL Agent. For information about the compatibility between BMC ProactiveNet and the BMC PATROL Agent, see BMC ProactiveNet and BMC PATROL Agent compatibility


BMC ProactiveNet Operations Console is enhanced to perform the following tasks:
•Plotting graph based on the data fetched from the BMC PATROL Agent directly
•Real-time status of agents and monitors
•Executing agent actions on a monitor
•Viewing annotation details from a graph
•Executing tasks on BMC PATROL Agents
•Setting the default console, page, or views when you log on to the console
•Resizing the Details notebook supports the Graph, Heat Map, Tile, and Canvas views.
•Changing the default Home Console
•Setting bookmarks as your homepage
•A new permission, View Console drop down options, enables or disables the Global Console and Local Server drop-down box, available on Central Server.  By default, all roles can view the Global Console and Local Server drop-down box. To change this behavior, edit the desired role from the Administration Console.  This permission works only in a Central-server environment and not in a single-server environment.

 

Localization Support:
Setting your display language, date and time format, and time zone preferences
In the BMC ProactiveNet Operations Console, you can set the display language, date and time format, and time zone based on which the date and time are displayed in the Operations Console and Central Monitoring Administration, if applicable.

 

New REST-based BMC ProactiveNet web services
You can use these web services to register or unregister the BMC ProactiveNet Child Servers with BMC ProactiveNet Central Monitoring Administration, list the available monitor solutions, versions, or monitor types, and create, delete, or update a policy.  For information about Central Monitoring Administration, see BMC ProactiveNet Central Monitoring Administration architecture

 


BPPM 9.5 Webinar

You spoke and we listened! BMC ProactiveNet Performance Management (BPPM) 9.5 delivers the most requested features asked for by customers. Join the webinar to hear about new capabilities that further establish BMC BPPM as the leading cross-domain performance monitoring and availability solution for the enterprise. This includes:

  • Built-in self-monitoring
  • Real time data streaming and guaranteed event and data delivery
  • Centralized automated administration and management of Patrol agents

 


Plus, learn how the largest US financial institution leveraged the new features of BPPM 9.5 to reduce IT costs while increasing user confidence in IT. The webinar will be hosted on Thursday, February 6, 2014 from 11:00am - 12:00 pm CST. Register here.

 


Introducing AMIGO!!!

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

Are you postponing an upgrade to the latest version of BMC ProactiveNet Performance Manager because of time, learning curve concerns or risk issues? Worry no more. The BPPM Assisting MIGration Operations (AMIGO) program is designed specifically to help you upgrade quickly, easily and safely.

 

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.


Spread the word AMIGO is here to help! https://communities.bmc.com/docs/DOC-28469

 

 

Computer.png

 

Popular Knowledge Articles:

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

KA345591 - dbsrv.exe process crashed with an assertion failure  

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

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

KA349786 -jserver (java_jsrv.exe) process continuously running 100% CPU since restarting BPPM server processes and no sign of it slowing down.

 

 

Feedback1.jpg

 


Was this helpful?  Are there related topics I missed? Please add comments to share your experience.

Share:|

Have you installed BPPM 9.0 SP2 yet? We have had many successful installations of BPPM 9.0 SP2 and while we await our 9.5 release, this is our most current version so if you are running an 8.x environment, we encourage you to upgrade. The Service Pack has been installed at many customer locations without issue.

 

Read about Service Pack 2 here:

https://docs.bmc.com/docs/display/public/PN90/Installing+Service+Pack+2+on+the+BMC+ProactiveNet+Server

 

There are over 75 fixes included in this Service Pack. The fixes cover all areas of the product such as:

  • Fixing graphs in the Operations Console, framing and toolbar fixes in the Operations Console
  • Fixes to management data published to the cell, cell connections, and cell crashes have been addressed 
  • Various errors such as NullPointer errors have been corrected
  • Group access permissions have been modified for viewing Devices
  • Modification and maintenance of various application parameters
  • SCOM Adapter corrections

 

To see a listing of all the fixes, review the details under Corrected issues in Service Pack 2
https://docs.bmc.com/docs/display/public/PN90/Corrected+issues+in+Service+Pack+2

Always remember, the first step to installing any Service Pack is to make sure you have a viable backup!

Here are some details for backing up the ProactiveNet Server on both Solaris and Windows:

Solaris:

The generic steps below should be sufficient to backup the configuration and data from the ProactiveNet Server running on Solaris.

  1. Shutdown the ProactiveNet Server.
    =======
    pw system stop
    =======
    Note: Verify all ProactiveNet Server processes are "!Not Running!" before creating the backup.
  2. Backup the ProactiveNet Server installation directory (/ProactiveNet/pw) using a TAR archive.
    =======
    cd /ProactiveNet
    tar cfp /backup/pronet_archive.tar pw
    =======
    Note: The Tar utility may complain about some files with very long names; these do not matter as they are only temporary files.
  3. Restore the ProactiveNet Server installation directory (/ProactiveNet/pw) over an existing installation of the same version which is not running (pw system stop).
    =======
    cd /ProactiveNet
    tar xvf /backup/pronet_archive.tar
    =======
    Note: Verify all ProactiveNet Server processes are "!Not Running!" before restoring the backup.

 

Additional details are documented in the Knowledge Base, "How to Migrate ProactiveNet Server to a different Solaris server?" https://kb.bmc.com/infocenter/index?page=content&id=KA294690

 

A backup of the "pw" directory is the most complete and direct way to archive the configuration and data from the ProactiveNet Server. The minimal list of files to archive the configuration and data is documented in the "Offline backup requirements" section, pages 18 - 21, of the "BMC ProactiveNet Performance Management: Disaster Recovery Best Practices"

http://documents.bmc.com/supportu/documents/34/03/193403/193403.pdf

 

Here are the instructions for Windows: Below are the steps to backup the ProactiveNet Server on Windows if the target ProactiveNet server (Windows) will have the SAME IP address and hostname as the original ProactiveNet server.


Step 1) The database archives are performed on a regular basis.  By default, the ProactiveNet server performs a full db archive once per week, with incremental archives once every day.

 

Step 2) Stop the ProactiveNet Server on the original server and backup the entire ProactiveNet Server installation directory.  The ProactiveNet Server installation directory can be determined by looking at the %PnServerPath% environment variable.  This is needed for restoring customized configuration files (custom monitors, Apache configuration, custom diagnostics, custom MIBs, etc.).  The running database file (located under the Sybase directory) can be left out of this particular backup since it will be restored separately from database archive (in general, a straight copy of a running database is not usable for archive purposes).

 

As a note, backing up the entire ProactiveNet Server installation directory should be performed at least on a semi-regular basis.  Also the archives should be kept on a separate physical disk from the ProactiveNet server installation to ensure maximum safety.

 

Note: There are no environment variables and Windows registry entries to backup for ProactiveNet Server on a Windows server.  The new ProactiveNet Server installation will take care of the environment variables and Windows registry entries and they are the same on all ProactiveNet Servers.

 

Below are the steps to restore the ProactiveNet Server on a target Windows server with the SAME IP address and hostname as the original ProactiveNet Server:

 

Step 1) Restore the Windows operating system and file systems.  Make sure there is a drive of the same name as the one on which ProactiveNet Server was originally installed.  If database archive was being sent to a different file system, make sure that drive name is also matched.

 

Step 2) Install the same ProactiveNet Server version as the original ProactiveNet Server.  Also install the same ProactiveNet patch as the original server ensuring to install to the directory of the same name as original.  Installing the ProactiveNet Server and patches ensures that all Windows environment variables and Windows registry entries are in place and all scheduled jobs are created properly.

 

Step 3) Stop the ProactiveNet Server on the target Windows server using the "pw system stop" command in the Pw Commands window or by stopping the services.

 

Step 4) Copy the backup of original ProactiveNet Server Installation directory on top of the new ProactiveNet Server installation on the target Windows server.

 

Step 5) If database archive is kept in a non-default location, restore it to that same location on the target Windows server making sure to use same drive and directory names (by default the database archive is kept under the %PnServerPath%\pw\dbarchive directory)

 

Step 6) Start the ProactiveNet Server on the target Windows server using the "pw system start" command in the Pw Commands window or by starting the services.

 

Step 7) Restore the database by running the "pw database restore" command in the Pw Commands window.

This completes the backup and restore procedure for the ProactiveNet Server with the same IP address and hostname as the original ProactiveNet Server.

 

Here are some of our reported issues and solutions while installing BPPM 9.0 Service Pack 2

ISSUE: Installation of BPPM 9.0 SP2 generates a rather lengthy list of warnings. Can these warnings be ignored or is further action required? Per BMC Engineering the majority of the warnings can be ignored, see KA402151 "BPPM 9.0 SP2 installation completes with warnings, is this problematic?'     https://kb.bmc.com/infocenter/index?page=content&id=KA402151

SOLUTION: There are 3 types of minor warnings in the log file but based on the contextual messages in the log these warnings can be safely ignored. These warnings have been verified by BMC Engineering and they can be ignored.

A) WARNING ---- SKIPPING VIEW /THRESHOLD/SIG THRESHOLD/POST INSTALL --Status CODE -->6
B) There is no Detailed Diagnostics deployment descriptors to register.
C) promail.MailSenderCLI

 

ISSUE: After installing BPPM 9.0 SP2 onto 3 Windows 2008 servers, two of the Windows servers are running the Integration Service. The PATROL Agent will not start showing an error code 3001.

The upgrade somehow changed the PATROL Agent to look in another directory for its config.default file. The PATROL Agent should be looking for the config.default in Patrol3\lib but it is looking in my pconfmgr directory. What should we do?

SOLUTION: While we do not have a root cause at this point for why the environment variables were changed, the solution is to reset the environment variables to the correct location. We have seen this issue only once and have not reproduced it internally so if any customers see this issue, please report it to Support so that we can investigate further.

 

ISSUE: I have downloaded the SP2 binary "BPPM_9022_CoreComponents_ServicePack_Linux.tar.gz" and am attempting to apply the patch to an Agent Cell by running the BPPMAgent9.0_b231178031.bin installation. When the installation gets to a certain point, it detects that there is already an active Cell on the system, and creates a "features selection error: Cell is already present on the system". There is no way to proceed with the SP2 install, cancellation is the only option. What should I do?

SOLUTION: This problem has been identified, and defect QM001775988 is opened on this.  In the meantime, the workaround from development is to install SP2 on a separate/new machine (as a fresh install), then copy the files to this machine that you need to upgrade.  The steps from development are:

  1. Install GA patch build in another machine with remote cell or IS option.
    2.            Copy files into the files to this machine.
    a.            Recommend to copy all files from <Install path>server\bin and <Install path>server\etc\default
    b.            For migrating KBs need to refer upgrade guide Appendix A "Using migrate utility".
    3.            Verify functionality.

The doc with the info for Migrating the cell kb is here: http://documents.bmc.com/supportu/documents/48/67/244867/244867.pdf Page 89.

 

ISSUE: After applying BPPM 9.0 SP2 the command 'penv -p "InitMgmtData=T" -e PROD init' failed. When I attempt to run this command it fails with the following: ‘penv -p "InitMgmtData=T" -e PROD init' failed

==> Request failure: Loading baroc data from file /appli/BPPMR/BppmServer/pw/server/etc/ps_lfpmsf1t/kb/data/.load failed. LoadException: loading files from /appli/BPPMR/BppmServer/pw/server/etc/ps_lfpmsf1t/kb/data/.load : astItem no instance of AstDef

SOLUTION: The issue is due to blanks at the end of the baroc files. Defect QM001806526 was created and fixed.  The files in the ps_xxxx data directory need to be modified to remove

Please edit each of the files in the data directory, do Ctrl-End to get to the end of the file then delete any extra lines that exist so the last line in each baroc file is just END. If you do make the changes and the problem still occurs, please edit again with a different editor to verify that no blank lines exist at the end of the file.  Some editors will ignore blank lines and others do not.

 

ISSUE: I am having issues in installing SP2 for BPPM 9.0.. It keeps throwing an error of: One or more files under pw directory in your installation are locked.

SOLUTION: Please download process viewer from windows sysnternals site form this link http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx, and then execute it please. Then select the Find option and enter the name of the file that is locked, so we can see which is process is handling such file.  We found that the Patrol Agent was using files in the ProactiveNet server path. So we stopped the Agent, configured the startup as manual, and set all the BPPM services to manual startup and rebooted the server. Once the install of SP2 was rerun the process ran smoothly and the SP2 installation was successful. There can be other processes causing a lock, but look to PATROL first.

Computer.png

 

Popular Knowledge Articles:

KA361960 - Is there a way to remove stale auto discovered devices from BPPM ? 

KA352096 - Unable to delete PATROL Adapter from ProactiveNet Admin Console  

KA359501 - How does the BPPM PATROL adapter auto-sync work?   

KA350682 - How can I install BPPM 8.6 with Oracle as the backend database ? How can I specify it is an Oracle RAC database? 

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

 

 

 

Feedback1.jpg

 

Was this helpful?  Are there related topics I missed? Please add comments to share your experience.

Filter Blog

By date:
By tag: