Beruflich Dokumente
Kultur Dokumente
2009 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Agenda
Introduction Log
files and tools wide problems nodes and processing problems and Web Access Server with NNMi Data in report pack
System No
Missing
Summary Reporting
Integrations
19 May 2010
Introduction
Data PI
Report
19 May 2010
Poller mw_collect
dpipe_snmp bcp_gateway dpipe_snmp dpipe_snmp
<raw>_upld1
<raw>_keys
Devices
4 19 May 2010
ODBC
Troubleshooting Outline
Based Check
the timer, database and Web Access Server (WAS) for major problems the data flow:
data is being collected and inserted trendpm raw-to-delta summaries and other processing reporting Check Check Check Check
Follow
19 May 2010
Tools
Management Log
Console Home/OVPI Status and Performance snap-in files script Support Online
19 May 2010
19 May 2010
Log Files
trend.log audit.log
the main log for PI data collection and processing start and stop times for processes amount of data collected
metrics.log
website0.log
19 May 2010
Log Files
report_<DATETIME>.log
19 May 2010
Log Files
Oracle JBoss
logs
10
19 May 2010
reports, NRT and Daily, in multiple report packs are empty Management Console / Home / OVPI Status check the trend.log for:
Check Next
11
19 May 2010
connections:
ODBC used by poller processes (mw_collect / pa_collect / ee_collect, bcp_gateway, trendpm) and trendcopy JDBC used by trend_sum, node_manager, Web Access Server Client used by ovpi_run_sql sqlplus on Oracle, isql on Sybase
Database
12
19 May 2010
System Performance
Check Check
indexmaint and db_delete_data run successfully each day they do not overlap if they do, adjust the trendtimer.sched GATHER_STATS_JOB recommendation is to disable this nightly Oracle job Oracle, involve your DBA to tune the database Sybase, use the dbtuner and see the additional tuning suggestions in the Admin Guide
13
19 May 2010
In case of hung trendpm, consider truncating the upload tables if they contain millions of rows
Check the trend.log on the server for trend_sum or SQL errors or hung processes for the datapipe or report pack
19 May 2010
14
If nodes are not in the correct Type groups, manually re-run Type Discover (from poller if applicable) If still not discovered, use ping and snmpwalk to verify connectivity, SNMP version, community string and MIB support
SNMP agents Type Discovered by trend_discover t Discovery runs each night on the PI server by default Uses SNMP v1 only
15
19 May 2010
16 19 May 2010
Check
NoSuchName
17
19 May 2010
Performance Agents (PA) or Operations Agents (OA) added to the OVPA Type group by OVPA_Collection_Daily.pro Discovery runs each night on the server by default
18
19 May 2010
the trend.log on the poller for messages relating to the missing server
For PA or OA, both success and failure logged
If
there are no messages for this server, recheck the OVPA Type (and View) group If there are "unable to ping" / "not pingable" messages in trend.log for this server, edit the {DPIPE_HOME}/data/pa_rpt.cnfg and change doping to: doping=no If still not collecting, use ovcodautil -ping to verify connectivity from the poller to target server
19 19 May 2010
20
19 May 2010
Slow Collections
Too
Default number of child collectors for mw_collect and pa_collect is 5 which is too low Edit the trendtimer.sched on each polling system and increase child collectors to 25 as a starting point by adding c 25 to the mw_collect and pa_collect entries
Overloaded
system
21
19 May 2010
processes, usually due to SQL hanging or running very slowly in the database:
Usually have to kill the hung process Ensure db_delete_data and indexmaint running Apply latest Patches or Hotfixes Tune database Reduce load if necessary
22
19 May 2010
Used to store metrics about collections that are displayed in Performance section of the Management Console Database can grow very large or be corrupted Can reduce retention and recreate Derby Database if needed
23
19 May 2010
Node Sync
Import list of managed nodes and their SNMP Read Community Strings from NNMi to PI PI then Type Discovers the node and starts polling NNMi v8.11 or later patches supported with PI 5.31 or later NNMi v9.0 supported with PI 5.41 Provides reports on NNMi Incidents NNMi v8.11 or later patches supported with Report Packs 14.0 (for PI 5.40) or later NNMi v9.0 supported with Report Packs 14.1 (for PI 5.41)
24
19 May 2010
nnmpi_wizard to configure on PI, nnmpi_cmd for automated sync to {DPIPE_HOME}/log/NNMPI_Wizard.log PI 5.40 upgrade to 5.41 or apply Hotfix 5.40.000 piweb HF05 NNMi 8 to the latest version available, currently NNM 8.x Patch 8
Patch
25
19 May 2010
the Incident and Availability Report Pack User Guide for information Logs to {DPIPE_HOME}/log/NNMi_Datapipe.log For Report Packs 14.0, upgrade to 14.1 (or apply Hotfix 5.40.000 piweb HF05) Patch NNMi 8 to the latest version available, currently NNM 8.x Patch 8 Ensure configuration follows KM752866 - PI server name needs to match systems.xml file Apply Hotfix for QCCR1B41849
26
19 May 2010
Packs 14.1
Problems after upgrading Service Assurance and Cisco SAA Datapipes from earlier versions (Does not impact new install of 14.1 versions of these packages) Upgrades to 14.1 (and 14.0) versions of the SystemResource_Disk and SystemResource_NetInterface from previous versions are extremely slow. Request Hotfixes before upgrading these packages.
27
19 May 2010
Questions?
28
19 May 2010
www.hp.com/go/swcommunity
29 19 May 2010