Troubleshooting data collection
Statistics collection for Application Assurance reports
A blank report may be due to a statistics collection issue, or a prompt selection that excludes all available data.
The description of the report shows the statistics type required for the report, and whether NSP flow collection is required.
Table 5-1, Troubleshooting statistics collection for Application Assurance reports describes options for checking statistics collection.
Table 5-1: Troubleshooting statistics collection for Application Assurance reports
Statistics type |
Items to verify |
See |
AA accounting |
-
Are required policies in place?
-
Are statistics being collected?
-
What is the accounting retrieval status of the NE?
-
Is additional information available from server performance statistics? |
“Workflow for accounting statistics collection” in the NSP NFM-P Statistics Management Guide
“Workflow for server performance statistics collection” in the NSP NFM-P Statistics Management Guide
“To view the accounting statistics collection status of an NE” in the NSP NFM-P Classic Management User Guide |
AA Cflowd |
|
“To enable and configure global Cflowd sampling on an NE” in the NSP NFM-P Classic Management User Guide
“To configure Cflowd collectors on an ISA-AA group or partition” in the NSP NFM-P Classic Management User Guide
“To configure an AA Cflowd group policy” in the NSP NFM-P Classic Management User Guide
“Workflow to configure flow statistics collection” in the NSP NFM-P Statistics Management Guide
If the report requires special study statistics collection, see “Workflow to configure AA Cflowd special study statistics collection” in the NSP NFM-P Statistics Management Guide |
Subscriber |
|
“To configure AA subscriber statistics collection on an ISA-AA group or partition” in the NSP NFM-P Classic Management User Guide |
Statistics and data collection for Network and Service reports and NSP reports
A blank report may be due to a statistics collection issue, or a prompt selection that excludes all available data.
The description of the report shows the statistics or data type required for the report, and any other prerequisites that may apply.
Table 5-2, Troubleshooting statistics and data collection for Network and Service reports and NSP reports describes options for checking collection.
Table 5-2: Troubleshooting statistics and data collection for Network and Service reports and NSP reports
Statistics type |
Items to verify |
See |
Accounting (also known as XML statistics) |
-
Are required policies in place?
-
Are statistics being collected?
-
Are required aggregators configured? |
“Workflow for accounting statistics collection” in the NSP NFM-P Statistics Management Guide
“How do I configure analytics aggregation?” in the NSP Analytics Report Catalog |
Performance (SNMP) data |
-
Are required policies in place?
-
Is SNMP connectivity established between the NE and the NFM-P?
-
Are required statistics being collected?
-
Are required aggregation rules enabled?
-
Alarms: if the system cannot collect and process all performance statistics in the specified polling period, the PollerDeadlineMissed alarm will be raised. |
“How do I configure analytics aggregation?” in the NSP Analytics Report Catalog |
IPFIX (also called System Cflowd or Netflow v10) |
|
“Workflow to configure flow statistics collection” in the NSP NFM-P Statistics Management Guide |
OAM data |
-
Is OAM testing configured in the NFM-P?
-
Are required policies in place?
-
Are OAM aggregation rules enabled? |
“How do I configure analytics aggregation?” in the NSP Analytics Report Catalog |
Event data for Uptime reports |
|
“To configure an event log policy” in the NSP NFM-P Classic Management User Guide
“To create and manage custom auxiliary database table attributes” in the NSP System Administrator Guide |
NSP auxiliary database
If you suspect an auxiliary database problem, you can run the following script on an auxiliary database station to collect log files for technical support:
/opt/nsp/nfmp/auxdb/install/bin/getDebugFiles.bash
NFM-P main database
For Inventory reports, the NFM-P main database must be operational and able to receive files from NEs.
To confirm that files are being received and stored, monitor the following folder on the standalone or primary main server to ensure that new statistics files are being generated:
/opt/nsp/nfmp/server/xml_output