Node Availability Summary report

Node Availability Summary report overview

The Node Availability Summary report shows availability information for NEs.

Use cases

Service level agreement—Use the report to validate that NE availability meets agreed targets.

Troubleshooting—Use the report to determine if an NE is currently, or has previously, been unavailable.

Limitations

When the report is exported to the RTF or DOCX file type, some columns may not display or there may be a problem with the table border.

Prerequisites

To create the report, NE availability must be determined. An availability framework computes periodic outage time and outage counts from state change records contained in the auxiliary database data dictionary. These periodic values are aggregated to determine the availability of an NE over a period of time. A periodic table tracks the activity state and availability of an NE.

The availability framework supports the creation of an availability table that aggregates the data in the periodic table based on the periodic synchronization time configured on the system. The object synchronization interval for tables registered for periodic calculation can be configured to run every 15 minutes, separately from the regular object synchronization task, by setting analyticsMODictPeriodicSyncTime in the nms-server.xml file on each NFM-P main server. See How do I synchronize the Analytics data dictionary table data with the NFM-P? for information.

You must also populate the maintenance window table in the auxiliary database with details of NE and Service maintenance; see To add data to the maintenance-window table in an auxiliary database. The report run if the table is not created or empty; however, maintenance windows are treated as downtime when availability is calculated.

Report characteristics

The following table lists the principal report characteristics.

Table 11-2: Node Availability Summary report characteristics

Characteristic	Value
Data type	Availability tables computed by availability framework
Source database	Auxiliary database
Report inputs	Prompt	Notes
	End date	Calendar date or relative date (for example, two days ago) and time
	Report range	Length of time to be reported, in minutes (minutes, min), hours (hours, h), days (days, d), weeks (w), or months (months, m)
	Granularity	Aggregation types: None (raw data) Hourly Daily Weekly Monthly
	Region
	Subregion	Only subregions below the top-level region are displayed in the prompt. Objects in the lower subregions are automatically selected when their subregion is selected.
	Uptime Threshold (%)	Identify the threshold percentage
	Downtime Threshold (Minutes)	Identify the downtime threshold in minutes
	Logo Resource ID	The logo to add to the report. Enter the Resource ID of the logo image in the Images folder. The default is the Nokia logo. To create the report without a logo, leave the Logo Resource ID field blank.
	Logo Position	Choose Left, Middle, or Right. The logo appears on the left on the first page of the report if you choose Left or Middle.
	Show report output on one page	Select the check box to enable pagination. Note: Using the Show report output on one page option when creating reports as drill-downs may impact report rendering time. Nokia recommends disabling the Show report output on one page option when creating reports.
Drill-down support	Yes—Click on a KPI in a table cell to launch the Details report

Example

The following figure shows a report example. Not all figures are from the same report.