Service Availability Details report

Service Availability Details report overview

The Service Availability Details report shows the availability details of services. The report provides graphs showing the maximum, minimum, and average availability of services.

Use cases

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

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

Prerequisites

To create the report, service 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 a service over a period of time. A periodic table tracks the activity state and availability of a service. The report does not consider the site, but instead uses the operational state of a service to provide the availability. Only the Up service is considered for Uptime; Partially Down and Down states are considered as downtime. 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 min (separate from the regular object synchronization task) by configuring analyticsMODictPeriodicSyncTime in the nms-server.xml file. See How do I synchronize the Analytics data dictionary table data with the NFM-P? for information about synchronizing the Analytics data dictionary table with the NFM-P.

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 will run if the table is not created or empty; however, maintenance windows are treated as down time when availability is calculated.

Report characteristics

The following table lists the principal report characteristics.

Table 11-23: Service Availability Details report characteristics

Characteristic	Value
Data type	Availability tables computed by availability framework
Source database	Auxiliary database
NE types supported	all 7210 SAS variants all 7250 IXR variants all 7705 SAR variants all 7750 SR variants
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	Select a 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.
	KPI	Max Availability Min Availability Avg Availability (for all granularities except for raw granularity) Availability (for raw granularity)
	Service(s)	Search using partial names or wildcard (%). Select an individual item.
	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	No

Example

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