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)
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?
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>]
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.
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.
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#
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:
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.
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
Help us determine how we are doing. Use the rating system at the bottom of this blog to rate this post!