The NFM-P provides a scalable platform for reliably collecting statistics from the managed NEs and the NFM-P system. The statistics are typically used for monitoring and troubleshooting an NFM-P network, and for SLA and billing functions.

Statistics collection must be enabled on the NFM-P before an OSS can retrieve them. Statistics collection can be performed on-demand or scheduled. See “Statistics collection in the NFM-P” in the NSP NFM-P Statistics Management Guide for more information.

The NFM-P can collect the following statistics:

• performance statistics—collected by polling NE MIBs, transferred to the NFM-P using SNMP, and stored in the NFM-P database

• accounting statistics—collected in files on NEs, transferred to the NFM-P using FTP or SCP, and stored in the NFM-P database

  Note:

  The NFM-P does not store AA accounting statistics in the NFM-P database. Instead, the NFM-P saves the statistics data in files for reporting in NSP Analytics reports, or for IPDR record processing by an OSS application. See “AA accounting statistics collection” in the NSP NFM-P Classic Management User Guide for more information.

• server performance statistics—collected from NFM-P system functions and processes, stored in the NFM-P database

• AA Cflowd statistics—collected from NEs using NSP Flow Collectors, can be stored in NSP auxiliary database or exported in IPDR format

• Cflowd statistics—collected from NEs by external collector; the NFM-P does not collect cflowd statistics or store in the NFM-P database

To collect statistics, the NFM-P requires policies that specify the following:

• the network or service objects from which to collect statistics

• the statistics counters to collect

• the collection rate

• how long the NFM-P is to retain the collected statistics data