NFM-P platform requirements for larger networks

Determining platform requirements for larger networks

NFM-P may require larger stations in order to successfully manage networks that exceed any of the dimensions supported by the minimum hardware platforms. In order to determine station requirements to successfully manage larger networks, the following information is required:

  • Expected number and types of network elements to be managed

  • Expected number of MDAs in the network to be managed

  • Expected number of services and SAPs in the network to be managed

  • Expected number of Dynamic LSPs to be deployed in the network

  • Maximum expected number of NFM-P clients (GUI) simultaneously monitoring the network

  • Expected number of XML-API applications that will connect as clients to the XML API interface

  • Expected number of subscribers, specifically for triple-play network deployments

  • Expected statistics collection and retention

  • Expected number of STM tests

  • Expected number of managed GNEs

  • Whether NFM-P redundancy is to be utilized

  • Whether NEBS compliance is required

  • Whether CPAM is required

  • Whether RAID 1 is required

The information above must then be sent to an Nokia representative who can provide the required hardware specifications.

Ensure that any projected growth in the network is taken into account when specifying the expected network dimensioning attributes. For existing NFM-P systems, the user may determine the number of MDAs deployed in the network using the help button on the GUI. It is also possible to determine the number of statistics being handled by the system by looking at the “Statistics Collection” information window. Select the “Tools”, then “Statistics”, then “Server Performance Statistics” menu. List the “Statistics Collection” objects. From this list window, check the “Scheduled Polling Stats Processed Periodic” and the “Accounting Stats Processed Periodic” columns for the performance and accounting statistics that your system is currently processing within the time interval defined by the collection policy (15 minutes by default).