NSP comprehensive reports information overview

General information

NSP comprehensive reports include network data for NEs managed by the NFM-P only, MDM (model-driven Nokia or multivendor NEs) only, or NFM-P+MDM-mediated NEs (for Node Health Summary and Node Health Details reports only). NSP comprehensive reports support a user experience where a large quantity of network data is fetched and rendered, then sorted and filtered for data mining purposes.

Summary reports contain many columns in an effort to put all relevant data into the table to avoid the need for multiple reports. In some cases, there may be a need to scroll horizontally to view all columns. The tables can be sorted and filtered on any column.

NSP comprehensive Details reports provide a time series linear graph of one of more selected KPI. The Details reports can be run directly or as a drill-down from the Summary report. From the Summary report, clicking on a KPI in a table cell automatically launches the Details report for that KPI.

These reports filter based on network topology/grouping, by region and subregion. Weekly granularity is also provided.

Note: Objects in subregions that are nested to three or more levels in depth are not displayed in the optional input prompts for region and subregion. When you do not select a region or subregion, objects are displayed in the report regardless of the levels. When you select any region or subregion, the objects available are displayed.

NSP comprehensive reports take more time to generate or return an exception when trying to render results in one page (when you select “Show report output on one page”) for a large amount of data.

If statistics are collected in both the NSP and NFM-P for the same NE, then the report displays the data randomly.

If the classic NE is discovered in the NSP with statistics enabled in the NFM-P, the input details are duplicated as both collection schema and samdb dictionary tables will have the entries.

Recommendations

Nokia recommends the following:

• Generate the reports over multiple pages, as aggregating a high number of pages of a report over a single page could take a considerable amount of time or may even fail.

• Schedule report generation for regions/subregions to ensure that there are no overlaps.

• Use the aggregated granularities for generating a report for a higher report range.

• Track memory utilization in the auxiliary database and manually clear it to ensure that there are no hung queries after the reports are cancelled.