0% found this document useful (0 votes)
90 views

BPPM v9.0 Best Practice Resolving Data Gapsv1.0

This document provides contact information for local and toll free phone numbers in many countries to participate in a BPPM Best Practice session. It includes local phone numbers for major cities around the world and toll free access numbers for international participants.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
90 views

BPPM v9.0 Best Practice Resolving Data Gapsv1.0

This document provides contact information for local and toll free phone numbers in many countries to participate in a BPPM Best Practice session. It includes local phone numbers for major cities around the world and toll free access numbers for international participants.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 40

BPPM Best Practice Resolving Data Gaps

Participant passcode: 461990


Int'l Toll and US Cell Phone: 913-312-0414 TOLL FREE:
US/CAN Toll free: 877-702-9054
Int'l toll free - Argentina: 0800 666 2571
LOCAL: Int'l toll free - Australia: 1 800 635 764
Local - Italy, Milan: +39 02 9978 1800 Int'l toll free - Netherlands: 0 800 024 9645
Int'l toll free - Austria: 0800 295 994
Local - Italy, Rome: +39 06 8743 4377 Int'l toll free - New Zealand: 0 800 440 611
Local - Australia, Brisbane: +61 (0) 7 3123 0047 Int'l toll free - Bahamas: 800 205 6295
Local - Japan, Tokyo: +81 (0) 3 4455 1996 Int'l toll free - Norway: 800 191 83
Local - Australia, Canberra: +61 (0) 2 6111 2007 Int'l toll free - Belgium: 0 800 72 785
Local - Latvia, Riga: +371 6601 3678 Int'l toll free - Panama: 00 800 226 7179
Local - Australia, Melbourne: +61 (0) 3 9034 3217 Int'l toll free - Brazil: 0800 891 8445
Local - Lithuania, Vilnius: +370 5205 5590 Int'l toll free - Philippines: 1 800 111 00400
Local - Australia, Sydney: +61 (0) 2 9126 3023 Int'l toll free - Bulgaria: 00 800 115 1110
Local - Luxembourg, Luxembourg: +352 2786 Int'l toll free - Poland: 00 800 112 41 37
Local - Austria, Vienna: +43 (0) 1 2675 904 Int'l toll free - Chile: 123 0020 9601
0224 Int'l toll free - Portugal: 800 819 382
Local - Bahrain, Manama: +973 1619 9040 Int'l toll free - China, Southern Region: 10 800 140
Local - Malaysia, Kuala Lumpur: +60 (0) 3 7724 Int'l toll free - Russian Federation: 810 800 2544
Local - Belgium, Brussels: +32 (0) 2 303 2273 1378
0847 1012
Local - Brazil, Sao Paolo: +55 11 3163 0461 Int'l toll free - Colombia: 01 800 518 0504
Local - Mexico, Mexico City: +52 55 4777 2663 Int'l toll free - Singapore, Singapore: 800 101
Local - Bulgaria, Sofia: +359 (0) 2 491 6411 Int'l toll free - Czech Republic: 800 142 277
Local - Netherlands, Amsterdam: +31 (0) 20 262 1738
Local - Canada, Montreal: +1 514 669 6112 Int'l toll free - Denmark: 8088-6980
0137 Int'l toll free - Slovenia: 0 800 80815
Local - Canada, Toronto: +1 647 426 9209 Int'l toll free - Dominican Republic: 1 888 751 4437
Local - New Zealand, Auckland: +64 (0) 9 929 Int'l toll free - South Africa: 0 800 999 562
Local - China: +86 400 120 2693 Int'l toll free - France: 0 800 914 669
1884 Int'l toll free - South Korea, Korea, Republic Of:
Local - China: +86 400 120 26 93 Int'l toll free - Germany: 0 800 182 4414
Local - Norway, Oslo: +47 21 95 32 33 003 0813 1654
Local - Czech Republic, Prague: +420 234 147 Int'l toll free - Greece: 00 800 161 2205 1068
Local - Poland, Warsaw: +48 (0) 22 295 36 31 Int'l toll free - Spain: 900 941 991
003 Int'l toll free - Hong Kong: 800 908 710
Local - Portugal, Lisbon: +351 21 120 9698 Int'l toll free - Sweden: 02 079 3671
Local - Denmark, Copenhagen: +45 78 78 79 63 Int'l toll free - Hungary: 06 800 184 72
Local - Romania, Bucharest: +40 (0) 21 529 1340 Int'l toll free - Switzerland: 0 800 896 853
Local - Estonia, Tallinn: +372 622 5742 Int'l toll free - India: 000 800 100 7363
Local - Russian Federation, Moscow: +7 495 620 Int'l toll free - Taiwan: 00 801 126 826
Local - Finland, Helsinki: +358 (0) 9 7479 0101 Int'l toll free - Indonesia: 001 803 011 2660
9818 Int'l toll free - Thailand: 001 800 12 066 3284
Local - France, Lille: +33 (0) 359 69 03 42 Int'l toll free - Ireland: 1 800 760 204
Local - Singapore, Singapore: +65 6416 9957 Int'l toll free - Trinidad and Tobago: 800 205
Local - France, Lyon: +33 (0) 426 10 30 24 Int'l toll free - Israel: 1 80 945 2068
Local - Slovakia (Slovak Republic), Bratislava: 7179
Local - France, Paris: +33 (0) 1 70 71 29 53 Int'l toll free - Italy: 800 873 593
+421 (0) 2 3278 6632 Int'l toll free - United Arab Emirates: 800 017
Local - Germany, Berlin: +49 (0) 30 2555 5430 Int'l toll free - Japan: 00531 12 0058
Local - Slovenia, Ljubljana: +386 (0) 1 888 8397 7175
Local - Germany, Frankfurt: +49 (0) 69 1200 9864 Int'l toll free - Korea, Republic Of: 00798 14 800
Local - South Africa, Johannesburg: +27 11 589 Int'l toll free - United Kingdom: 0 800 051 7166
Local - Germany, Munich: +49 (0) 89 1436 7911 4574
8382 Int'l toll free - Uruguay: 000413 598 2551
Local - Hong Kong, Hong Kong: +852 3008 0383 Int'l toll free - Latvia: 800 03 656
Local - Spain, Madrid: +34 91 080 0153 Int'l toll free - Venezuela: 0 800 100 2525
Local - Hungary, Budapest: +36 1 577 9957 Int'l toll free - Lithuania: 88 003 0200
Local - Sweden, Stockholm: +46 (0) 8 4030 4953
Local - India, Bangalore: +91 (0) 80 6127 5134 Int'l toll free - Luxembourg: 800 25 164
Local - Switzerland, Geneva: +41 (0) 22 555 0258
Local - India, Mumbai: +91 (0) 22 6150 2334 Int'l toll free - Malaysia: 1 800 812 644
Local - Switzerland, Zurich: +41 (0) 44 556 8481
Local - Ireland, Dublin: +353 (0) 1 437 0560 Int'l toll free - Mexico: 001 800 514 1058
Local - Taiwan, Taipei: +886 (0) 2 2650 7292
Local - Israel, Tel Aviv: +972 (0) 3 721 9373 Int'l toll free - Monaco: 800 93 304
Local - United Kingdom, London: +44 (0) 20 8150
0796 Participant passcode: 461990

© 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

Resolving Data Gaps


Legal Notice

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.

© Copyright 7/19/2013 BMC Software, Inc 3


Overview

First Level Training

Best Practice vs. How To

Covers Core BPPM Components

Does not address every scenario

Basic knowledge of BPPM is helpful

© Copyright 7/19/2013 BMC Software, Inc 4


Webinar Material

BPPM 9.0 Best Practices


- https://communities.bmc.com/communities/docs/DOC-21385

BPPM 8.6 Best Practices


- https://communities.bmc.com/communities/docs/DOC-18448

Content
- Recorded Sessions
- PowerPoint presentations
- Questions & Answers

© Copyright 7/19/2013 BMC Software, Inc 5


Agenda

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

© Copyright 7/19/2013 BMC Software, Inc 6


BPPM Architecture Review

© Copyright 7/19/2013 BMC Software, Inc 7


BPPM Architecture Review

Event Path Enablement


- PATROL agent configured for event filtering
- PATROL agent configured for event propagation to IS
- IS node BEM cell configured to process events
- IS node BEM cell configured to event propagation to BPPM server

Trend Data Path Enablement


- “Admin” IS nodes is connected to BPPM server
- PATROL agent is connected to “Admin” IS node
- Monitor Types are imported from application classes
- Production IS nodes are connected to the BPPM server
- Adapters are created
- PATROL agents are connected to pproxy on IS nodes

CMA Policy Application Enablement


- Policies are defined with tag values
- PNet agent is connected to BPPM server
- PNet agent registers pproxy with CMA in BPPM server
 Requires pproxy.enabled = true
 For manual workflow set pproxy.enabled = false after
registration and restart the PNet agent
- PATROL agent is configured with a policy tag value
- PATROL agent is connected to pproxy on IS node

NOTE: - pproxy is the “Integration Service” OS process


- arrows indicate how connections are established
© Copyright 7/19/2013 BMC Software, Inc 8
BPPM Architecture Review

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

Trend Data Flow


- PATROL Agent sends data to pproxy Integration Service
 NOTE: P3 adapters initiate the connection and polls
- PNet Agent gets data from pproxy
- PNet Agent sends data to Agent Controller on BPPM server
- Jserver processes data from Agent Controller

CMA Policy Propagation Flow


- PATROL Agent connects to pproxy Integration Service
- PNet agent sends PATROL agent tag information to BPPM server
- pproxcli connects to Integration Service (pproxy)
- PATROL Agent gets policies from Integration Service

NOTE: - pproxy is the “Integration Service” OS process


- arrows indicate how connections are established

© Copyright 7/19/2013 BMC Software, Inc 9


BPPM Architecture Review

Integration Service Node Use Cases


- “Admin” Integration Service Node
 Do Not use to create adapters
 Import PATROL application classes to create monitor types
 Use for event configuration validation
 Use in all environments
- Production General Data Collection
 Windows local agents
 UNIX local agents
- Production Domain Data Collection
 vSphere KM connected to vCenter
 Remote OS Monitoring
 Remote Monitoring in vBlock
– UCS Manager
– Storage
– Hardware
 A single large 3rd party source (ex. SCOM)
 CLM “Data Collection Host”

© Copyright 7/19/2013 BMC Software, Inc 10


BPPM Server Tuning & Configuration

Create the following files if they do not already exist


- …/pw/custom/conf/pnjserver.conf
- …/pw/custom/conf/pnrate.conf
- …/pw/custom/conf/pnagentcntl.conf

Copy the #Variable Section# data from the default settings


- From the corresponding files in …pw/pronto/conf
- To the corresponding files in …/pw/custom/conf

Edit Memory Settings


- Heap needs to be increased for all environments
- Set minimum heap ¼ of maximum heap
- Examples provided here are for a large environment

© Copyright 7/19/2013 BMC Software, Inc 11


BPPM Server Tuning & Configuration

Jserver memory (pnjserver.conf)


- MinHeap=2048m
- MaxHeap=8192m

Rate Process memory (pnrate.conf)


- MinHeap=2048m
- MaxHeap=8192m

Agent Controller memory (pnagentcntl.conf )


- MinHeap=1024m
- MaxHeap=4096m

Verify DB Caching is 25% of server memory


- Sybase running on Windows
- …pw/pronto/conf/pndbsrv.conf
- COMDefine –ch 25%

© Copyright 7/19/2013 BMC Software, Inc 12


BPPM Server Tuning & Configuration

Set timeouts, thread limits, connection limits, pool sizes, etc.


- …pw\custom\conf\pronet.conf
- pronet.apps.agent.agentmon.agentstatusrefreshperiod=180000
- pronet.apps.agent.watchdog.sleeptime=120000
- pronet.apps.agent.pollperiod.allowednoreplies.tcp=4
- pronet.jvm.maxthreadlimit=50000
- pronet.apps.agent.pollperiod=180000
- pronet.jserver.cachemodule.threadpool.max.size=40
- pronet.jserver.databasemodule.threadpool.max.size=40
- pronet.rate.maxdbconnections=100
- pronet.jserver.dbconnectionpool.maxdbconnections=50
- pronet.apps.agentcontroller.msghandler.workerpoolsize=30
- pronet.apps.agentcontroller.dbwriter.maxmsgcachelimit=60000
- pronet.apps.monitortypediscovery.timeout=1800000
- mo.snmpmo.resolveIP=false
Stop and start the BPPM server
- pw system stop
- pw system start
© Copyright 7/19/2013 BMC Software, Inc 13
PNet Remote Agent Tuning & Configuration

Create a custom agent configuration file


- …/BPPMAgent/Agent/custom/conf/pnagent.conf
- Copy the #Variable Section# data from the default settings
 From the pnagent.conf file in …BPPMAgent/Agent/pronto/conf
 To the pnagent.conf file in …BPPMAgent/Agent/custom/conf

Configure memory settings


- …/BPPMAgent/Agent/custom/conf/pnagent.conf
- MinHeap=2048m
- MaxHeap=8192m

Configure Sleeptime, Threads, Poll Period, & Threads


- …/BPPMAgent/Agent/custom/conf/pronet.conf
- pronet.apps.agent.watchdog.sleeptime=120000
- pronet.jvm.maxthreadlimit=100000
- pronet.apps.agent.pollperiod=180000

© Copyright 7/19/2013 BMC Software, Inc 14


PNet Remote Agent Tuning & Configuration

Set Adapter Behavior


- …/BPPMAgent/Agent/custom/conf/pronet.conf

- Supporting Manual workflow adapters


 pronet.apps.agent.patrol.proxy.enabled=false *
 pronet.apps.agent.pproxy.watchdog.enabled=true **

- Supporting Auto workflow adapters


 pronet.apps.agent.patrol.proxy.enabled=true
 pronet.apps.agent.pproxy.watchdog.enabled=false

Increase the PATROL adapter poll count


- Applies only to Integration Service nodes supporting PATROL agents
- …/Agent/pw/monitors/shared/MF3PatrolAdapter/MF3PatrolAdapter.conf
- pnpollcount =15

* 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

PATROL Agent General Data Collection


PATROL_CONFIG
"/AgentSetup/historyRetentionPeriod" = { REPLACE = "3" },
"/AgentSetup/Identification/Tags/TAG/MSWindows" = { REPLACE = "Windows default monitoring" },
"/AgentSetup/integration/integrationServices" = { REPLACE = "tcp:change_me:3183" },
"/AgentSetup/integration/useFQDNHostName" = { REPLACE = "yes" },
"/AgentSetup/loadOnlyPreloadedKMs" = { REPLACE = "yes" },
"/AgentSetup/preloadedKMs" = { REPLACE = "ALL_COMPUTERS.km,AS_EVENTSPRING.km,NT_LOAD.kml,NT_BASE.kml,PATROL_NT.km" },
"/EventSetup/Configuration/EventCells" = { REPLACE = "change_me/1828" },
"/EventSetup/Configuration/Format" = { REPLACE = "BiiP3" },
"/EventSetup/Configuration/Key" = { REPLACE = "mc" },
"/EventSetup/Format/BiiP3/active" = { REPLACE = "0" },
"/EventSetup/Format/BiiP3/catalogs/0/active" = { REPLACE = "0" },
"/EventSetup/Format/BiiP3/catalogs/0/types/11/active" = { REPLACE = "1" },
"/EventSetup/Format/BiiP3/catalogs/0/types/9/active" = { REPLACE = "1" },
"/EventSetup/Format/BiiP3/class" = { REPLACE = "PATROL_EV" }

PATROL Agent for vSphere


PATROL_CONFIG
"/AgentSetup/preloadedKMs" = { REPLACE = "ALL_COMPUTERS.km,AS_EVENTSPRING.km,PATROL_NT.km,VSM.kml" },
"/AgentSetup/integration/useFQDNHostName" = { REPLACE = "yes" },
"/AgentSetup/AgentTuning/runqSchedPolicy" = { REPLACE = "2" },
"/AgentSetup/AgentTuning/pslInstructionMax" = { REPLACE = "0" },
"/AgentSetup/loadOnlyPreloadedKMs" = { REPLACE = "yes" },
"/AgentSetup/fixHistFlag" = { REPLACE = "Dirtybit" }

© Copyright 7/19/2013 BMC Software, Inc 17


PATROL Agent Tuning & Configuration Rules

PATROL Agent for vSphere KM specific settings


PATROL_CONFIG
"/VSM/Global/DEBUG" = { REPLACE = "0" },
"/VSM/Global/SERVICE_URL" = { REPLACE = “vCenterHost.company.com;443;domain\\userID" },
"/VSM/Global/CollectorType" = { REPLACE = "0" },
"/VSM/VC/ceops-admin-01.bmc.com/DeviceHostnameLookupOrder" = { REPLACE = "DNSNAME" },
"/VSM/VC/ceops-admin-01.bmc.com/FilterClusters" = { REPLACE = ".*1" },
"/VSM/VC/ceops-admin-01.bmc.com/FilterDatacenters" = { REPLACE = ".*1" },
"/VSM/VC/ceops-admin-01.bmc.com/FilterHosts" = { REPLACE = ".*1" },
"/VSM/VC/ceops-admin-01.bmc.com/FilterVMS" = { REPLACE = ".*1" },
"/VSM/VC/ceops-admin-01.bmc.com/FilterVMSDNS" = { REPLACE = ".*1" },
"/VSM/VC/ceops-admin-01.bmc.com/FilterVMSIP" = { REPLACE = ".*1" },
"/VSM/VC/ceops-admin-01.bmc.com/IncludeVMTemplates" = { REPLACE = "0" },
"/VSM/VC/ceops-admin-01.bmc.com/jre64" = { REPLACE = "1" },
"/VSM/VC/ceops-admin-01.bmc.com/HostScsiExclude" = { REPLACE = "1" }

© Copyright 7/19/2013 BMC Software, Inc 18


Major Implementation Steps

Do Not configure and activate at the same time


- Methodically control the process
- Configure first, test second, activate last
- Configure
 Adjusting tuning, timeouts, and other basic settings in
configuration files
 Import application classes to create monitor types using
the Admin IS node
- Activate
 Connect components in production
 Allow data and events to flow in production

Configure infrastructure components


- BPPM Server
- Integration Service Nodes
- PNet Remote Agents
- Event Cells
Do Not connect PATROL agents initially

© Copyright 7/19/2013 BMC Software, Inc 19


Major Implementation Steps

Data Collection First


- Do not connect everything together initially
 Integration Service & Event Setup
– Use “changeme” integration configuration to control connections
- Install agents & KMs
- Configure data collection * *
- Validate data collection in PATROL console * *

Import Application Classes to create Monitor Types


- Use the Admin Integration Service Node to control import and update of monitor types
- Connect sample PATROL agents to Admin IS node
 If the PATROL agent is already in production use P3 adapter to poll the PATROL agent
- Import application classes to create Monitor Types
- Do Not complete the process by adding the adapter
 You are only using the Admin IS node to create monitor types in the BPPM server

* If using Policies in CMA, configuration & validation will be in the BPPM console later except for test nodes.

© Copyright 7/19/2013 BMC Software, Inc 20


Major Implementation Steps

Configure ProactiveNet Remote Agent


- Supporting Auto workflow adapters
 Recommeded for
– “Standardized” collection (ex Data Collection Host, only vCenter, etc)
– Where filtering application classes and/or parameters is not needed
– An IS node can only have one adapter if it uses an auto workflow adapter

 Settings in pronet.conf file


pronet.apps.agent.patrol.proxy.enabled=true
pronet.apps.agent.pproxy.watchdog.enabled=false **

- Supporting Manual workflow adapters


 Recommeded
– Where filtering application classes and/or parameters is required
– Where controlling data volume and unnecessary parameters is necessary
– An IS node can have multiple manual adapters as long as the adapters control unique monitor types

 Settings in pronet.conf file


pronet.apps.agent.patrol.proxy.enabled=false
pronet.apps.agent.pproxy.watchdog.enabled=true **

** Watchdog was implemented in BPPM versions 8.5 SP5, 8.6 SP3 and 9.0.

© Copyright 7/19/2013 BMC Software, Inc 21


Major Implementation Steps

Add Integration Service nodes in the Admin Console


- When adding either add with pproxy.enabled=false or add with no agents connected

Add Adapters in BPPM Admin console


- Skip importing application classes
- Set appropriate synchronization and poll times
 Example for a large vCenter
– at least 1 hour synchronization frequency
– at least 45 minute timeout

- Times can be reduced after initial discovery


 Assumes no future complete rediscovery
 Assumes no significant change in number of discovered devices, instances, etc.
 Most successful environments leave this set to 1 hour and 45 minutes for all adapters

© Copyright 7/19/2013 BMC Software, Inc 22


Major Implementation Steps

Prevent PATROL agents from initially connecting to the IS node(s)


- Use “ChangeMe” integration variable values
Do Not Configure PATROL agents for IS nodes until
- Data collection at the PATROL agents is configured and satisfactory
- You have imported PATROL application classes as Monitor Types
 Conducted through the “Admin” IS node
 Using sample PATROL agent(s) connect to the “Admin” IS node
- The Integration Service node(s) are configured
- You have configured event filtering at the PATROL agents

Configure PATROL agents for IS nodes


- Configure PATROL agents for appropriate IS nodes
- Active general collection in groups, not all at once (example a few hundred at a time)
- Add domain collecting PATROL agents one at a time
- Allow time for discovery & synchronization
 Manual Discovering Adapters
 Auto Discovering Adapter
 Can take over an hour for large data sources

© Copyright 7/19/2013 BMC Software, Inc 23


Verifying Data Collection

Validate data collection in BPPM console

Verify Data Collection Consistency


- http://<bppm_server>/snapshots

© Copyright 7/19/2013 BMC Software, Inc 24


Verifying Data Collection

BPPM Data Consistency Report


- Provides information on data gaps
- Enable on the BPPM server
- Recommend not enabled for long periods of time (months)
- Disable when not needed

Enabling the Data Consistency Report


- Edit the pronet configuration file
 …/pw/custom/conf/pronet.conf
pronet.rate.datagapcheck.enable=1
pronet.rate.datagapcheck.emailNotification=1
pronet.rate.datagapcheck.checkinterval=60
pronet.rate.datagapcheck.xmlfileretention=30
pronet.rate.datagapcheck.senddetailedoutput=1
- Restart the rate process
 pw p r rate
- View the report
 http://<BPPM Server Hostname>/jsp/DataGapStat.jsp.

© Copyright 7/19/2013 BMC Software, Inc 25


Verifying Data Collection

© Copyright 7/19/2013 BMC Software, Inc 26


Verifying Data Collection

Data Gap Consistency Report


- To launch the report
 http://<bppm_server>/jsp/DataGapStat.jsp.
- Knowledge Article KA363827
 https://kb.bmc.com/infocenter/index?page=content&id=KA363827

Data Collection Status Report


- To launch the report
 http://<bppm_server>/snapshots
- Knowledge Article KA354229
 https://kb.bmc.com/infocenter/index?page=content&id=KA354229

© Copyright 7/19/2013 BMC Software, Inc 27


Troubleshooting Data Gaps

Start from data collection at the source and work up stream


- Verify the source PATROL agent is/was collecting data
- Use a PATROL console
- Compare the time periods
Verify the source PATROL agent is connected to the Integration Service
- Verify network connectivity
- Check PATROL agent error log for connectivity to IS node
- Check for the PATROL agent in the Integration Service
- Review self monitoring and log files to see if the source agent lost connection to the Integration
Server during the period of No Data
Review self monitoring and log files for the Integration Server
- Processes
 Integration Service (pproxy)
 ProactiveNet Remote agent
 pprocy cli
 mcell
- Issues to look for
 Process stop/start times
 Connectivity errors
 Time out errors
 Heap utilization
© Copyright 7/19/2013 BMC Software, Inc 28
Troubleshooting Data Gaps

IS node PatrolAdapter.log showing issue getting data from PATROL agent


- In this case the agent was down

C:\Program Files\BMC Software\BPPMAgent\Agent\pronto\logs\PatrolAdapter.log

© Copyright 7/19/2013 BMC Software, Inc 29


Troubleshooting Data Gaps

IS node ProactiveNetAgent.log showing issue connecting to agent controller on


BPPM server
- In this case the agent controller was down

C:\Program Files\BMC Software\BPPMAgent\Agent\pronto\logs\ProactiveNetAgent.log

© Copyright 7/19/2013 BMC Software, Inc 30


Troubleshooting Data Gaps

BPPM Server ProactiveNet.log showing issue connecting to PNet Remote agent


- In this case the agent was down

C:\Program Files\BMC Software\ProactiveNet\pw\pronto\logs\ProactiveNet.log

© Copyright 7/19/2013 BMC Software, Inc 31


Troubleshooting Data Gaps

Verify the ProactiveNet remote agent is properly configured


- Synch times
- Poll Times
- Time outs
- Threads
- Heap settings
Verify the adapter(s) are properly configured
- P3 or SA Adapter
- Check adapter collection filtering
 Devices
 Application Classes
 Instances
 Parameters

Verify BPPM server configuration (all processes)

© Copyright 7/19/2013 BMC Software, Inc 32


Partial Data Missing

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

© Copyright 7/19/2013 BMC Software, Inc 33


Data missing for specific Patrol Agents

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

© Copyright 7/19/2013 BMC Software, Inc 34


Global Data Missing

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

© Copyright 7/19/2013 BMC Software, Inc 35


Current BPPM versions

As of this presentation date, the current versions and patch levels of BMC
ProactiveNet Performance Manager (BPPM) are:

- BPPM 8.6 SP4


- BPPM 9.0 SP1 (9.0.20)
C:\Users\Administrator>pw version

BMC ProactiveNet 9.0.00 build 231155897 [Windows]


BMC ProactiveNet Agent 9.0.00 build 231155897 [Windows]
Service Pack 9.0.20

© Copyright 7/19/2013 BMC Software, Inc 36


Upgrade Recommendation

Upgrade to BPPM version 8.6 SP 4


- Released June 28, 2013
Upgrade to BPPM version 9.0 SP 1 (9.0.20)
- Consider this version as a baseline
- Upgrade all components
 Server
 IS nodes
 Agents
- Many product improvements
- Improved Integration Service and data collection stability
- Improved device assignment and data organization

BPPM version 9.0 SP 2


- Target release date August/September 2013

© Copyright 7/19/2013 BMC Software, Inc 37


Current BPPM version

BMC Electronic Product Download (EPD)

© Copyright 7/19/2013 BMC Software, Inc 38


Current BPPM version

Downloaded file
BPPM_9020_CoreComponents_ServicePack_Windows.zip

Command Line Verification

© Copyright 7/19/2013 BMC Software, Inc 39


© Copyright 7/19/2013 BMC Software, Inc 40

You might also like