BPPM v9.0 Best Practice Resolving Data Gapsv1.0
BPPM v9.0 Best Practice Resolving Data Gapsv1.0
© Copyright 7/19/2013 BMC Software, Inc NOTE: Some locations do not support cell phones and require a land line. 1
BMC ProactiveNet Performance Management
Best Practices
All of the recommendations and information described herein are at the sole
discretion of BMC Software, are subject to change and/or cancellation, and in no
way should this content be viewed as guarantees or warrantees on BMC’s part.
Content
- Recorded Sessions
- PowerPoint presentations
- Questions & Answers
Architecture Review
Preventing Data Gaps - Tuning & Configuration
Major Implementation Steps
Verifying Data Collection
Troubleshooting Data Gaps
Scenario 1 – Partial Data Missing
Scenario 2 – Data missing for specific Patrol Agents
Scenario 3 – All data missing for at least one Integration Service node
Event Flow
- PATROL Agent generates event
- PATROL Agent sends event to BEM cell on IS node
- IS node BEM cell processes event
- IS node BEM cell sends event to BPPM server cell
* Must be initially set to true for PNet Remote Agent registration with CMA for Policy based management
** Available in BPPM 8.5 SP5, 8,6 SP3 and 9.0 SP1
© Copyright 7/19/2013 BMC Software, Inc 15
PATROL Agent Tuning & Configuration
Ensure that all PATROL agents are properly tuned for the data they are collecting
- Preloaded KMs
- Load only Preloaded KMs
- Minimized number of KMs listed in Preloaded and Disabled KM lists (use KMLs)
- Ensure Fully Qualified Domain Names
- History retention
- Restrict event propagation
- Etc.
Additional tuning required for domain data collection from large sources
- PATROL for vSphere
- PATROL for Windows Remote
- PATROL for UNIX/Linux Remote
- vBlock Monitoring
UCS Manager
Storage
Hardware
- CLM Data Collection Host
© Copyright 7/19/2013 BMC Software, Inc 16
PATROL Agent Tuning & Configuration Rules
* If using Policies in CMA, configuration & validation will be in the BPPM console later except for test nodes.
** Watchdog was implemented in BPPM versions 8.5 SP5, 8.6 SP3 and 9.0.
Behavior
- Data gaps in trends for some parameters
- Is not global
- Typically isolated to one or more of the following
A specific KM / Monitor type and instance
A specific PATROL agent
A single Integration Service node
Common Causes
- KM / Monitor Instance dropped out of PATROL
- PATROL agent
Unstable PATROL agent connectivity
PATROL agent was stopped and restarted
Incorrect PATROL agent tuning configuration
PATROL agent history corruption
PATROL agent / KM functionality has been altered due to a connection from the
PATROL Classic Console in developer mode
- Integration Service
Ran out of heap memory on Integration Service node
Behavior
- All data is not coming into the BPPM server for a specific PATROL agent
- Data for other agents connected to the same IS node is coming in
Common Causes
- PATROL agent is or was down
- Network Connection problems from the PATROL agent to the IS node
- Extreme PATROL agent history corruption
- PATROL agent security is incorrectly configured
- Incorrect PATROL agent / KM configuration setting(s) in pconfig rules
- PATROL agent functionality has been altered due to a connection from the PATROL
Classic Console in developer mode
Behavior
- All data missing from an Integration Service node
- All data missing across all Integration Service nodes
Common Causes
- All data missing from a specific Integration Service node
IS has been shutdown or disconnected from the BPPM server
Network connectivity issue
Improper IS PNet agent configuration
pproxycli process is down
PNet agent cannot communicate to controller
pproxy PATROL security corrupted or missing
- All data missing across all Integration Service nodes
Network problem
Agent Controller down
Agent Controller incorrectly configured
Significant BPPM server configuration/tuning issues
As of this presentation date, the current versions and patch levels of BMC
ProactiveNet Performance Manager (BPPM) are:
Downloaded file
BPPM_9020_CoreComponents_ServicePack_Windows.zip