-
Copyright 12/6/2012 BMC Software, Inc 1
INTERNATIONAL TOLL FREE
BPPM 9.0 Best Practice Data Collection
Argentina 0 800 444 6440
Australia 1 800 612 415
Austria 0 800 295 780
Bahamas 1 800 389 0491
Belgium 0 800 75 636
Brazil 0 800 891 0266
Bulgaria 00 800 115 1141
Chile 123 0020 6707
China, North 10 800 714 1509
China, South 10 800 140 1376
Colombia 01 800 518 1171
Czech Republic 800 700 715
Denmark 80 883 277
Dominican Republic 1 888 752 0002
France 0 800 914 176
Germany 0 800 183 0299
Greece 00 800 161 2205 6440
Hong Kong 800 968 066
Hungary 06 800 112 82
India 000 800 1007 613
Indonesia 001 803 017 6440
Ireland 1 800 947 415
Israel 1 80 925 6440
Italy 800 789 377
Japan 00348 0040 1009
Latvia 8000 3523
Lithuania 8 800 3 09 64
Luxembourg 800 2 3214
Malaysia 1 800 814 723
Mexico 001 800 514 6440
Monaco 800 39 593
Netherlands 0 800 022 1465
New Zealand 0 800 451 520
Norway 800 138 41
Panama 00 800 226 6440
Peru 0 800 54 129
Philippines 1 800 111 010 55
Poland 00 800 112 41 42
Portugal 800 827 538
Russian 810 800 2915 1012
Singapore 800 101 2320
Slovenia 0 800 80439
South Africa 0 800 982 304
South Korea 003 0813 2344
Spain 900 937 665
Sweden 02 079 3266
Switzerland 0 800 894 821
Taiwan 00 801 127 186
Thailand 001 800 156 205 2068
Trinidad & Tobago 1 800 205 6440
United Kingdom 0 808 101 7156
Uruguay 0004 019 0348
Venezuela 0 800 100 8540
NOTE: Local numbers are not available. Some locations do not
support cell phones and require a land line.
-
BMC ProactiveNet Performance Management v9.0
Data Collection
-
Copyright 12/6/2012 BMC Software, Inc 3
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 BMCs part.
-
Copyright 12/6/2012 BMC Software, Inc 4
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 12/6/2012 BMC Software, Inc 5
Agenda
Overall RecommendationsEvent DataPerformance DataRemote
AgentsPATROL for VMware vSphereTransaction ManagementAvoiding
Duplicate DevicesSelf Monitoring
-
Copyright 12/6/2012 BMC Software, Inc 6
Overall Recommendations
-
Copyright 12/6/2012 BMC Software, Inc 7
Overall Recommendations
Do not collected unnecessary data- Disable collection at the
agent(s)
Unnecessary application classesIdentify the proper KM file(s)
and do not load them to the agentExample: NT_JOBS
Disable instances where possibleExample: Monitor only important
windows services
Do not waste time disabling parameters at the agentsData will
not be collected at the agent howeverParameters will appear in BPPM
with no data
- Filtering at the Integration Service Node(s)Define parameter
filtering
Cannot be edited after importing the related application
classDefine Instance filteringDefine host filtering
Both host and instance filtering can be edited after importing
application classes.All filtering will be done at the agent in a
future release and parameter filtering will be editable.
-
Copyright 12/6/2012 BMC Software, Inc 8
Overall Recommendations
Establish Standards- Basic Monitoring
CPUMemoryDiskAvailability
- In-Depth MonitoringBasic MonitoringSpecific Processes &
ServicesLogfilesNetwork I/OEtc.
- Business NeedCriticalityRevenueDevelopment, Test,
Production
Establishing standards also helps you size the solution
accurately and ensures the administrators know what to expect.
-
Copyright 12/6/2012 BMC Software, Inc 9
Overall Recommendations
Separate Configuration Activities- Tools Configuration
Installing the componentsSetting tuning valuesSetting agent
variablesAdding remote ProactiveNet agents
- Data Consumption ConfigurationCreating adaptersEditing
adaptersConnecting agents
Performance dateEvent data
-
Copyright 12/6/2012 BMC Software, Inc 10
Overall Recommendations
Major Configuration Steps- First - Define Standards
- Second Configure Transaction Management (TM ART)Create
projectsDeploy transactions to execution serversConfigure TM ART
BPPM Adapter
- Third - Configure PATROLConfigure all agents for localhost
Pay attention during install !Integration Service nodes Event
cell
Monitoring & TrendingAvailability & Critical Event
Generation
-
Copyright 12/6/2012 BMC Software, Inc 11
Overall Recommendations
Major Configuration Steps (continued)- Fourth - Configure
Integration Services
Add the event cells to the admin cell and the BPPM server
Disable auto discovering adapter capability
C:\Program Files\BMC
Software\BPPMAgent\Agent\custom\conf\pronet.confpronet.apps.agent.patrol.proxy.enabled=false
Restart the remote ProactiveNet agent
Add IS node in the BPPM Admin console
Reset the pronet.conf file
C:\Program Files\BMC
Software\BPPMAgent\Agent\custom\conf\pronet.confpronet.apps.agent.patrol.proxy.enabled=true
Restart the remote ProactiveNet agent
-
Copyright 12/6/2012 BMC Software, Inc 12
Overall Recommendations
Major Configuration Steps (continued)- Fourth - Configure
Integration Services (continued)
Connect sample PATROL agents not allReplace localhost with the
proper Integration Service node and port
Create AdaptersManually Import Application ClassesImport only
application classes based on standardsFilter parameters according
to standardsFilter Instances & Hosts
Configure agents for integration service in groups of a
hundredReplace localhost with the proper Integration Service node
and port
Configure event propagation and apply to all agent nodesReplace
localhost with the proper event cell node and port
-
Copyright 12/6/2012 BMC Software, Inc 13
Overall Recommendations
Architecture & Global Considerations- Deploy Collection
Components physically close to the
managed nodes Integration Service Nodes Remote Monitoring
vCenter Operating System Web Servers, Oracle DB, etc.
- Use Fully Qualified Domain Names (FQDN) Ensure Agents report
managed hosts as FQDN Exception: Multiple agents on a single
node
Alias Host Name
- PATROL Agent & KM Configuration Pre-load the KMs to be
used for monitoring Do not use the Classic Console for
administration
Exceptions: Small environments with few usersEnvironments
already using the console
-
Copyright 12/6/2012 BMC Software, Inc 14
Overall Recommendations
Architecture & Global Considerations (continued)- When to
use a dedicated Integration Service node
vCenter Remote Monitoring Large performance data volume from a
single source
Examples: TM ART, Entuity, etc Large external event volumes
Examples: SNMP Traps, Tivoli, Netcool, etc
- Allocate dedicated resources for all management nodes Do not
share memory, CPU, etc on virtual nodes
- Integration Service Nodes & AdaptersNo not configure auto
discovering adapters
Default configuration Only useful if all PATROL configuration
covers exactly what is needed
Trended availability metrics? Unwanted parameters?
-
Copyright 12/6/2012 BMC Software, Inc 15
Overall Recommendations
Integration Service Node Use Cases- Common Use
Processes performance and event data from local agents Adapters
should all be configured the same way on all
For example adapters for UNIX and Windows should be configured
the same on all Allows you to point any managed node running a
local agent to any Common Use IS node
- Enterprise Dedicated for a specific high volume data
source
vCenter TM ART Entuity Eye of the Storm
Configure highly restricted adapters for these specific data
sources
- Event onlyDedicated to processing large numbers of events
SNMP TrapsEvents from a third party enterprise event manager
Tivoli, Netcool, etc.
-
Copyright 12/6/2012 BMC Software, Inc 16
Event Data
Events to generate in PATROL- Availability Parameters
Service Up/DownProcess Up/DownDiskspace fullEtc.
- Boolean ParametersLog file monitoringCollectorCPU tempsFan
SpeedOthers (learn the KMs)
- Do not trend these parameters in the BPPM serverUnnecessary
resource consumptionGuaranteed Event Alerting
-
Copyright 12/6/2012 BMC Software, Inc 17
Event Data
Event Management & Propagation Methods- BPPM 9.x Agent &
Rules
Recommended MethodBetter PerformanceEliminates need for BII4P3
and Notification ServersEvent Filtering Required
Default configuration - All state changes are processed as
eventsConfigure PATROL agents so that you are not generating events
for
every state change
- Event Management KMUse in existing environments where already
in use and migrateNot recommendedWill be phased out over timeLower
performanceMigrate to BPPM 9.x Agent & Rules
-
Copyright 12/6/2012 BMC Software, Inc 18
Event Data
Event Process Migration to PATROL 9.0 Agent- Both leverage
PATROL configuration rules- No migration utility- Major migration
steps
Update agents on the Notification Servers to 9.xConfigure
Notification Servers
Define rules to send only NOTIFY events directly to cell(s)
Disable/Decommission BII4P3Update monitoring for all agents to
send events
directly to cellsComplete in phasesDisable notify events
Disable/Decommission Notification ServersNotification Server
agents can be repurposed
Self monitoring on IS nodeRemote monitoring on Dedicated
node
-
Copyright 12/6/2012 BMC Software, Inc 19
Event Data
Provide a secondary path for events- Reasons
BPPM Server Maintenance BPPM Server OS Cluster outage
- Method Setup a stand-by secondary event
management node Configure additional propagation policy on
each Integration Service node Critical events flow to through
the primary and
the secondary path Secondary path can be disable when not
needed by simply disabling the related propagation policy
-
Copyright 12/6/2012 BMC Software, Inc 20
Performance Data
Integration Service Nodes & Adapters- Components
Integration Service process Gathers data from PATROL agents
Remote PNet Agent Gathers data from Integration Service
Process
Adapters Configuration data Tells the Remote PNet agent what
data to gather
- Recommendations Each PNet remote agent should be associated to
one and
only one Integration Service process
The Integration Service process should be associated to one and
only one PNet remote agent
The corresponding PNet remote agent and Integration Service
process should be installed on the same node
-
Copyright 12/6/2012 BMC Software, Inc 21
Performance Data
Integration Service Nodes & Adapters- Adapters (PATROL)
Integration Service Node Association Each adapter can be
associated to one
and only one remote PNet agent
Auto Discovering Automatically created Default setting One per
Integration Service node Not recommended
Manual Discovering Manually Created Multiple per Integration
Service node Recommended
-
Copyright 12/6/2012 BMC Software, Inc 22
Performance Data
Running Multiple Integration Service Processes & Remote PNet
agents pairs- Multiple pairs can run on one node- Follow the
preceding guidance (one to one relationship per pair, etc)-
Allocate appropriate resources- Assign unique ports and follow a
standard
Example:A instances: ports 3182, 3183, etcB instances: ports
3192, 3193, etc
- The install allows only one cell on a node
Windows Performance Monitor KM Wizard- Out of the box KM creates
an excessively large number of instances (huge)- The value
parameter is hard to report on and for BCO to handle- Create a
custom KM to resolve these issues
-
Copyright 12/6/2012 BMC Software, Inc 23
Performance Data
Do- Configure manual discovering adapters
- Filter and exclude monitored data from the source up First at
the agent Second in the adapter configurations
- Configure multiple adapters per Common Use Integration Service
node Typically one per KM solution (Windows, Unix, etc.)
- Standardize the adapter configuration(s) across all Common Use
Integration Service nodes
- Create a unique adapter per application class when integrating
to the BMC Portal
- Ensure a one to one relationship between remote PNet agents
and Integration Service process
- Pre-load only necessary KMs
- Minimize the number of KMs referenced in the pre-loaded and
disabled KM lists Including what is referenced by KMLs
-
Copyright 12/6/2012 BMC Software, Inc 24
Performance Data
Do Not- Use auto discovering adapters (default)
Exceptions vSphere, limited Remote Monitoring
- Collect Boolean metrics for trending
- Configure one big adapter for all Common Use PATROL
integrations
- Set synchronization at the adapters faster than polling
frequencies at the agents
- Mix Common Use and Enterprise type collection on one
Integration Service and remote PNet agent pair (or Integration
Service node)
- Use random port numbers (follow a logical standard)
- If all KMs in a KML are not needed do not put the KML in the
preloaded list
- Increase polling frequencies unnecessarily
-
Copyright 12/6/2012 BMC Software, Inc 25
PATROL Agent Remote Monitoring
Dedicated Nodes- PATROL Agents- Multiple Agents
Can run on one nodeAllocate resources properlyAssign port
numbers logically
Agent 1 port: 3181Agent 2 port: 3191
Windows Considerations- WinRM is required on the managed
nodes
UNIX/Linux Considerations- SSH increases overhead- SSH requires
managing security
-
Copyright 12/6/2012 BMC Software, Inc 26
PATROL Agent Remote Monitoring
Do- Use for light-weight monitoring- Install the agent and KMs
on dedicated node(s)- Configure multiple agents on single dedicated
node(s) with unique port
numbersFollow a standard port numbering scheme
- Increase resources for the agent in large environments (Ex. 10
Gb ram for vSphere)
Do Not- Use remote monitoring for log file monitoring- Monitor
the same managed nodes from multiple remote agents- Use remote
monitoring if an agent is installed on the managed node
locally
-
Copyright 12/6/2012 BMC Software, Inc 27
PATROL for VMware vSphere
Prerequisites- VMware Tools installed on each guest- vCenter Web
Service- User in vCenter with read only permissions from top
directory tree down
Dedicated Resources- Use a dedicated PATROL Agent running the
Virtual Servers KM only.- Use a dedicated node for the PATROL
agent- Use a dedicated Integration Service Node
ESX Monitoring Connectivity- vCenter- ESX 3.5 and up- Do not use
both
-
Copyright 12/6/2012 BMC Software, Inc 28
PATROL for VMware vSphere
Fully Qualified Domain Names- Set DeviceHostnameLookupOrder =
DNSNAME, VMNAME- Ensure the agents on the guest operating systems
are also configured for FQDN
Guest Operating System Metrics- Inaccurate metrics in local
guest OS
CPU Memory Gather these metrics from the VMware vSphere KM
Configure Filtering- Datacenters- DNS names & IP addresses-
VM Templates
-
Copyright 12/6/2012 BMC Software, Inc 29
PATROL for VMware vSphere
Sizing & Scalability- Install on 64 bit hardware and OS-
Dedicated 64-Bit 8Gb ram Integration Service node
1 Patrol agent 2000 VM guest hosts
- Dedicated 64-Bit 16Gb ram Integration Service node 1 Patrol
agent 2400 VM guest hosts
Recommended PATROL Agent Settings- History retention to one day-
Pre-load only the vSphere required KMs- Force the agent to only
load pre-loaded KMs- Set automated agent history repair- Force DNS
names for all guest nodes- Allocate at least 10 Gb of ram for the
PATROL agent- Reduce Chunk Size in large environments
Start with 50 Reduce to 25 if 50 is too big
- Set the agent runqSchedPolicy to 2
-
Copyright 12/6/2012 BMC Software, Inc 30
PATROL for VMware vSphere
Recommended PATROL Agent Settings (continued)- On nodes with
multiple NICs bind the agent to a single IP- Disable custom events-
Filter DNS names for VM guests- Set publishHostName so that the
agent has a unique name in BPPM
Recommended Remote ProactiveNet Agent Settings- MinHeap=2048m-
MaxHeap=4096m- LOCMaxHeap=512m
Do- Load the vSphere KM on a dedicated PATROL agent- Use a
dedicated Integration Service node (or pair of processes) for
collecting
data from the vSphere KM
Do Not- Use the same Integration Service node (or pair of
processes) for vSphere and
local agent collection- Create the adapter while connected to a
large environment
-
Copyright 12/6/2012 BMC Software, Inc 31
Transaction Management
PATROL for Internet Servers (ISM KM)- Synthetic Basic URL
Monitoring
Response Time Content Errors
End User Experience Monitor (EUEM)- Real User Transactions
Response Time Content Errors
Transaction Management Application Response Timer (TM ART)-
Synthetic Business Transactions
Response Time Content Errors Multiple steps/screens
-
Copyright 12/6/2012 BMC Software, Inc 32
Transaction Management
TM ART Integration Methods- TM ART KM
Older methodRequires a dedicated PATROL agent and KMUse
Cases
Temporary integration if ProactiveNet will be implemented at a
later timeTo provide continued monitoring when the ProactiveNet
server is under maintenance
- TM ART ProactiveNet AdapterNewer methodRequires the
ProactiveNet server No PATROL agent and KM requiredShould use a
dedicated Integration Service node
-
Copyright 12/6/2012 BMC Software, Inc 33
Transaction Management
TM ART Adapter Benefits- Collects more parameters
custom counters custom timersproject measurements
- Separates transaction data from accuracy data- Supports
flashchecks- Provides automated or manual detailed diagnostic
actions
Detailed page timer data Generate a TrueLog diagnostic file
Integrate with BMC AppSight
- Parameter timestamp based on the BMC TM ART Execution
ServerMatches the Execution Log values in BMC TM ART Central.
- Better optimized data collection- Eliminates BMC ProactiveNet
data gaps and inconsistency
-
Copyright 12/6/2012 BMC Software, Inc 34
Transaction Management
TM ART High Availability- Central Server
OS Clustering
- Execution ServersLeverage Location groupings
- WorkbenchBackup/Restore
-
Copyright 12/6/2012 BMC Software, Inc 35
Avoiding Duplicate Devices
Enforce Fully Qualified Domain Names- Local PATROL monitoring-
Remote PATROL monitoring- VMware- CMDB- Everywhere
Stale Cleaner- Identifies empty groups and devices- Deletes
empty groups and devices- Requires stopping the BPPM server and
starting only the database and cell- Get help from BMC Software
Customer Support
-
Copyright 12/6/2012 BMC Software, Inc 36
Self Monitoring
PATROL Agents & KMs- PATROL Local Agents- PATROL for BMC
ProactiveNet Self Monitoring
BPPM Diagnostics- BPPM GUI- BPPM JSP Pages
Impact Management - Built-In Component Monitoring- Admin Service
Model
-
Copyright 12/6/2012 BMC Software, Inc 37
Self Monitoring - PATROL Agents & KMs
PATROL Local Agents- Built-in at the agent- PATROL Agent
Performance- PATROL Agent Errors- Collector Status
PATROL for BMC ProactiveNet Self Monitoring KM- BPPM server
monitoring- Integration Service node monitoring- Auto Discovery
BPPM server Integration Service nodeComponents
-
Copyright 12/6/2012 BMC Software, Inc 38
Self Monitoring - PATROL Agents & KMs
PATROL for BMC ProactiveNet Self Monitoring KM (continued)-
Operating system level monitoring- Component monitoring
Critical processes BMC ProactiveNet Server Integration
Service
- Status monitoring and data collectionPATROL Agents connected
to the Integration Services Number of PATROL Agents connected
Number of PATROL Agents disconnectedData collection status
Connection status
- Supports out of the box Integration Service node
failoverAccounts for PATROL Agent failover to a different
Integration ServiceConfigure out of the box integration service
node failover if using this feature
- Email notificationRequires Blat
-
Copyright 12/6/2012 BMC Software, Inc 39
Self Monitoring - PATROL Agents & KMs
Do- Install a dedicated agent instance for self monitoring
BPPM Server Integration Service nodesRemote monitoring
nodesStandalone event management nodesOther management nodes (TM
ART Central, BCO, etc)
- Consider using a service model- Assign a unique port to the
agents and make this a standard (Ex 3381)- Pre-load the KMs
Do Not- Share an agent with other KMs that are monitoring the
managed
environment- Use the management infrastructure you are
monitoring to process events
and notification- Forget to plan hardware resources
-
Copyright 12/6/2012 BMC Software, Inc 40
Self Monitoring Impact Management
Built-In Component Monitoring & Administrative Service
Model
-
Copyright 12/6/2012 BMC Software, Inc 41
Additional Resources & Information
Online Documentation- BPPM 9.0 Product Documentation
https://docs.bmc.com/docs/display/public/PN90/Home
BMC Communities (public forum)- BMC website
https://communities.bmc.com/communities/community/bmcdn/service_assurance
documents discussions whitepapers additional information
-
Copyright 12/6/2012 BMC Software, Inc 42