Service and Customer Utilization Summary reports overview

General information

Service and Customer Utilization Summary reports show utilization percentage information for a service or customer.

Note: The utilization data is derived from collected statistics. It will not be an exact match to utilization data available via CLI from the NE.

Prerequisites

The following items need to be performed in the NFM-P for Service and Customer Utilization Summary reports to be created:

• QoS policies must be configured for the NEs on which statistics are to be collected; see the NSP NFM-P Classic Management User Guide for information about QoS policies. The policies must be associated with the SAP on which statistics are to be collected.

• Configure the customer in the NFM-P. Customer names must be unique.

• A file policy and a Complete Service Ingress Egress accounting policy must be configured for the NEs on which statistics are to be collected; see the NSP NFM-P Statistics Management Guide for information about creating file and accounting policies.

  The file and accounting policies must be assigned to the SAPs that belong to services for which the Utilization reports will be created.

• To view the report for granularities other than raw data, the following aggregation rules must be enabled; see How do I configure analytics aggregation?.

  Note:The reports combine all aggregation tables for both 7750 SR/7705 SAR and 7210 SAS, therefore all the following aggregations need to be enabled to generate a report for either NE type.

  • SAP Interface Stats Aggregator Ingress and SAP Interface Stats Aggregator Egress must be enabled for 7750 SR and 7705 SAR NEs.

  • Service Ingress Octets Aggregator and Service Egress Octets Aggregator must be enabled for 7210 SAS NEs.

• For raw data, the periodic counter must be enabled from the Periodic Counter Manager; see information in the NSP NFM-P Statistics Management Guide about creating and managing periodic accounting statistics calculations

Note: Customer Utilization Summary and Customer Uptime Summary reports may not complete if they are run on customers with more than 100 000 services.