Other NSP components minimum platform requirements
Minimum hardware platform requirements
The following tables specify the minimum hardware platform requirements necessary to successfully operate the various NSP components in a bare metal configuration.
The minimum platform requirements also represent the smallest configurations suitable for lab evaluations and demonstrations of the NSP product.
Bare metal hardware configurations
Table 2-13: NFM-P bare metal minimum collocated platform
For networks not exceeding: | |
|---|---|
|
NFM-P application |
x86 architecture |
|
NFM-P server and database (Collocated) |
6* Intel x86 CPU Cores (12 Hyper-threads), minimum 2.0GHz 1 46 GB RAM recommended (37 GB RAM minimum) 4*10K RPM SAS disk drives of at least 300 GB in size is required for performance and storage capacity |
Notes:
2.0GHz only supported on Skylake and newer CPU microarchitecture. Minimum speed on CPUs older than Skylake is 2.4GHz.
Table 2-14: NFM-P bare metal minimum distributed platform
For networks not exceeding: OR | |
|---|---|
|
NFM-P application |
x86 architecture |
|
NFM-P server |
6* Intel x86 CPU Cores (12 Hyper-threads), minimum 2.0GHz 1 41 GB RAM recommended (33 GB RAM minimum). 2*10K RPM SAS disk drives of at least 300 GB each in size |
|
NFM-P database |
4* Intel x86 CPU Cores (8 Hyper-threads), minimum 2.0GHz 1 32 GB RAM minimum. 4*10K RPM SAS disk drives of at least 300 GB in size is required for performance and storage capacity |
Notes:
2.0GHz only supported on Skylake and newer CPU microarchitecture. Minimum speed on CPUs older than Skylake is 2.4GHz.
Minimum VM resource requirements
The following tables list the minimum VM resource requirements for deployments of various NSP components using VMware vSphere ESXi or RHEL KVM.
The minimum platform requirements also represent the smallest configurations suitable for lab evaluations and demonstrations of the NSP product.
VM minimum collocated resource requirements
Table 2-15: NFM-P VM minimum collocated configuration
For networks not exceeding: | |
|---|---|
|
NFM-P application |
VM Guest hardware resource requirements |
|
NFM-P server and database (collocated) |
12 vCPUs, minimum 2.0GHz 1 46 GB RAM recommended (37 GB RAM minimum) 800 GB disk space I/O requirements found in Storage |
Notes:
2.0GHz only supported on Intel Xeon Skylake and newer CPU microarchitecture and AMD Epyc Zen 3 microarchitecture. For Intel CPUs, the minimum speed on CPUs older than Skylake is 2.4GHz.
The minimum resource requirements above are also applicable in situations where the NFM-P application is installed in a redundant configuration.
VM minimum distributed resource requirements
Table 2-16: NFM-P VM minimum distributed configuration
For networks not exceeding: OR | |
|---|---|
|
NFM-P application |
VM Guest hardware resource requirements |
|
NFM-P server |
12 vCPUs, minimum 2.0GHz 1 41 GB RAM recommended (33 GB minimum) 500 GB disk space I/O throughput and latency as provided in NFM-P sizing response |
|
NFM-P database |
8 vCPUs, minimum 2.0GHz 1 32 GB RAM minimum 1000 GB disk space I/O throughput and latency as provided in NFM-P sizing response |
Notes:
2.0GHz only supported on Intel Xeon Skylake and newer CPU microarchitecture and AMD Epyc Zen 3 microarchitecture. For Intel CPUs, the minimum speed on CPUs older than Skylake is 2.4GHz.
All of the minimum hardware platforms above are also applicable in situations where the NFM-P application is installed in a redundant configuration.
Scaling limits for collocated configurations
Collocated NFM-P configurations have been capped at the maximums described in the following table. Higher numbers may be achievable, but Nokia will only support the stated maximums. Note that all stated maximums may not be achievable simultaneously.
Table 2-17: Scaling limits for collocated configurations
|
Scaling parameter |
Maximum |
|---|---|
|
Number of MDAs |
1,875 |
|
Number of Simultaneous NFM-P clients (GUI or XML-API) |
25 |
|
Number of SAPs |
600 000 |
|
Number of OAM tests per 10 minute interval |
1000 |
|
Performance statistics per 15 minute interval |
50 000 |
|
Accounting statistics per 15 minute interval |
200 000 |
|
TCAs |
50 000 |
Minimum platform requirements for NFM-P auxiliary collectors
Table 2-18: NFM-P auxiliary platforms - Bare Metal
|
Architecture |
Supported NFM-P auxiliary type |
Configuration |
|---|---|---|
|
Bare Metal x86 |
statistics collector |
4 * Intel x86 CPU Cores (8 Hyper-threads), minimum 2.0GHz 1 12 GB RAM minimum. 16 GB RAM is recommended. 4*10K RPM SAS disk drives of at least 300 GB each in size |
Notes:
2.0GHz only supported on Intel Xeon Skylake and newer CPU microarchitecture. Minimum speed on CPUs older than Skylake is 2.4GHz.
Table 2-19: NFM-P auxiliary platforms - VM
|
Architecture |
Supported NFM-P auxiliary type |
Configuration |
|---|---|---|
|
VMware/KVM |
statistics collector |
8 vCPUs, minimum 2.0GHz 1 12 GB RAM minimum. 16 GB RAM is recommended. 600 GB disk space I/O throughput and latency as provided in NFM-P sizing response |
Notes:
2.0GHz only supported on Intel Xeon Skylake and newer CPU microarchitecture and AMD Epyc Zen 3 microarchitecture. For Intel CPUs, the minimum speed on CPUs older than Skylake is 2.4GHz.
Minimum platform requirements for NSP auxiliary database
Table 2-20: NSP auxiliary database platform - single node cluster
|
Architecture |
Configuration | |
|---|---|---|
|
Bare Metal x86 |
4 * Intel x86 CPU Cores (8 Hyper-threads), minimum 2.0GHz 1 64 GB RAM minimum. 2 SAS 10K RPM disk drives of at least 300 GB each in size (RAID 1) + 4 SAS 10K RPM disk drives of at least 1.2TB each in size (RAID 1+0) + 4 SAS 10K RPM disks of at least 1.2TB each in size (RAID 5) | |
|
VMware/KVM |
8 vCPUs, minimum 2.0GHz 2 64 GB RAM minimum. 500+ GB disk space I/O throughput as measured with the vioperf utility | |
Notes:
2.0GHz only supported on Intel Xeon Skylake and newer CPU microarchitecture. Minimum speed on CPUs older than Skylake is 2.4GHz.
2.0GHz only supported on Intel Xeon Skylake and newer CPU microarchitecture and AMD Epyc Zen 3 microarchitecture . Minimum speed on Intel CPUs older than Skylake is 2.4GHz.
Table 2-21: NSP auxiliary database platform - three+ node cluster
|
Architecture |
Configuration (for each node of the auxiliary database cluster 1) | |
|---|---|---|
|
Bare Metal x86 |
12 * Intel x86 CPU Cores (24 Hyper-threads), minimum 2.0GHz 2 128 GB RAM minimum. 2 SAS 10K RPM disk drives of at least 300 GB each in size (RAID 1) + 12 SAS 10K RPM disk drives of at least 600 GB each in size (RAID 1+0) + 5 SAS 10K RPM disks of at least 1.2TB each in size (RAID 5) Minimum of two 1Gb network interfaces. One dedicated to inter-cluster communication. | |
|
VMware/KVM |
24 vCPUs, minimum 2.0GHz 3 128 GB RAM minimum. Dedicated network interface for inter-cluster communication only. 500+ GB disk space I/O throughput as measured with the vioperf utility simultaneously on all nodes in the cluster | |
Notes:
Minimum of three nodes required in the cluster.
2.0GHz only supported on Intel Xeon Skylake and newer CPU microarchitecture Minimum speed on CPUs older than Skylake is 2.6GHz.
2.0GHz only supported on Intel Xeon Skylake and newer CPU microarchitecture and AMD Epyc Zen 3 microarchitecture. Minimum speed on Intel CPUs older than Skylake is 2.6GHz.
Platform requirements for NFM-P client delegate server stations
NFM-P allows multiple clients to be installed on a single HP x86 or Nokia AirFrame station running RHEL 8 server x86-64, or specific versions of Windows. This option enables customers to launch multiple NFM-P clients from a single station. These GUI clients can be displayed using a Citrix client/Server, or additionally in the case of RHEL, the X11 protocol to other desktops, or native X displays.
The client delegate server platform provides an option to consolidate multiple installations of the NFM-P client onto a single station where one instance of the NFM-P client is run by many users (with unique Operating System accounts).
The amount of memory listed includes the requirement for the NFM-P java UI and web browser. Additional memory for each NFM-P client will be required for management of the network elements described in Network element specific requirements .
Management of certain network elements may include the cross-launch of additional software that may not be compatible with certain operating systems. The information in Table 2-24, Element manager operating system support summary lists these element managers and their operating system support. See the element-manager documentation to determine current operating system support.
The NFM-P client delegate server configuration is only supported on specific HP or Nokia AirFrame x86 stations running RHEL server x86-64, or specific versions of Windows. Additionally, the NFM-P client delegate server installation is supported on a Guest Operating System of a VMware vSphere ESXi or RHEL KVM installation. The Guest OS must be one of those supported for GUI clients. Table 2-22, Minimum NFM-P client delegate server resource requirements describes resource requirements for this type of station.
Table 2-22: Minimum NFM-P client delegate server resource requirements
|
Architecture |
Configuration |
|---|---|
|
Bare Metal x86 |
4* Intel x86 CPU Cores (8 Hyper-threads), minimum 2.0GHz 28 GB RAM minimum, 36 GB for networks with greater than 15 000 NEs 1*10K RPM SAS disk drive, 146 GB in size |
|
VMware/KVM |
8 vCPUs, minimum 2.0GHz 28 GB RAM minimum, 36 GB for networks with greater than 15 000 NEs 70 GB disk space |
The configurations in the preceding table will support up to 15 GUI clients. Additional GUI clients can be hosted on the same platform provided that the appropriate additional resources found in Table 2-23, Additional client NFM-P client delegate server resource requirements are added to the platform.
Table 2-23: Additional client NFM-P client delegate server resource requirements
|
Architecture |
Additional resources per client |
|---|---|
|
Bare Metal x86 |
1/4 * Intel x86 CPU Core (1/2 Hyper-thread), minimum 2.0GHz 1.75 GB RAM, 2.25 GB for networks with greater than 15 000 NEs 1 GB Disk Space |
|
VMware/KVM |
1/2 vCPU, minimum 2.0GHz 1.75 GB RAM, 2.25 GB for networks with greater than 15.000 NEs 1 GB Disk Space |
For situations where more than 60 simultaneous GUI sessions are required, Nokia recommends deploying multiple NFM-P client delegate servers.
Displaying GUI clients to computers running X-emulation software is not currently supported. In cases where the GUI client is to be displayed to a PC computer running Windows, Nokia supports installing the GUI client directly on the PC.
NFM-P supports using Citrix for remote display of NFM-P clients. Supporting Citrix on the delegate platform requires extra system resources that will need to be added to those that are required by the NFM-P delegate. See the Citrix documentation to determine the additional Citrix resource requirements.
The following Citrix software has been tested with the Windows client delegate server:
Due to an incompatibility between 64-bit versions of the Firefox web browser and Citrix Server XenApp, the default web browser must be set to either Google Chrome, if using a version of XenApp older than 7.14.
The client delegate server can be published in XenApp by installing the delegate server on your delivery controller and then publishing the <delegate install directory>\nms\bin\nmsclient.bat file as a manually published application.
NFM-P client platform requirements
Nokia recommends having a minimum of 1.75 GB of dedicated RAM – regardless of the operating system, for the NFM-P client which includes the java UI and web browser memory requirements. In cases where other applications are running on the same platform as the NFM-P client, it is important to ensure 1.75 GB RAM is available to meet the NFM-P client requirements.
Additional memory for each NFM-P client will be required for management of the network elements described in Network element specific requirements .
Management of certain network elements may include the cross-launch of additional software that may not be compatible with certain operating systems. The information in the following table lists these element managers and their operating system support. See the element-manager documentation to determine current operating system support.
Table 2-24: Element manager operating system support summary
|
Element manager |
Node type |
RHEL 8 server support |
Microsoft Windows support |
|---|---|---|---|
|
NEtO |
9500 MPR / Wavence SM |
Not-supported |
Supported |
The following table provides the minimum requirement for the hardware that will host NFM-P GUI client software. Additional memory and disk resources will be required by the Operating System.
Table 2-25: NFM-P client hardware platform requirements
|
NFM-P client hardware platform requirements | |
|---|---|
|
RHEL platforms |
Microsoft Windows |
|
1 Intel CPU (2 Hyper-threads)@ 2.0 GHz or higher 1.75 GB RAM dedicated to NFM-P client, 2 GB for networks with greater than 15 000 NEs 1 GB available disk space 1280*1024 Display resolution for Java GUI (recommended) 1280*720@72ppi Display resolution for NFM-P applications (minimum) 1920*1080@72ppi Display resolution for NFM-P applications (recommended) Example platform: DL380 Gen10 |
1 Intel CPU (2 Hyper-threads)@ 2 GHz or higher 1.75 GB RAM dedicated to NFM-P client, 2 GB for networks with greater than 15 000 NEs 1 GB available disk space 1280*1024 Display resolution for Java GUI (recommended) 1280*720@72ppi Display resolution for NFM-P applications (minimum) 1920*1080@72ppi Display resolution for NFM-P applications (recommended) |
An NFM-P client installation is supported on a Guest Operating System of a VMware vSphere ESXi or RHEL KVM installation. The Guest OS must be one of those supported for GUI clients.
The following table provides the dedicated NFM-P resource requirements for each Guest OS running under VMware vSphere ESXi or RHEL KVM that will be used to host the NFM-P client GUI. This does not include the specific operating system resource requirements which are in addition to the hardware resources listed below. CPU and Memory resources must be reserved and dedicated to the individual Guest OSs and cannot be shared or oversubscribed. Disk and network resources should be managed appropriately to ensure that other Guest OSs on the same physical server do not negatively impact the operation of the NFM-P GUI client.
Table 2-26: Virtualized NFM-P client resource requirements
|
VM resource requirements | ||
|---|---|---|
|
RHEL Guest OS resources |
Microsoft Windows Guest OS resources | |
|
2 vCPUs @ 2GHz or higher 1.75 GB dedicated RAM, 2 GB for networks with greater than 15 000 NEs 1 GB available disk space 1280*1024 Display resolution for Java GUI (recommended) 1280*720@72ppi Display resolution for NFM-P applications (minimum) 1920*1080@72ppi Display resolution for NFM-P applications (recommended) |
2 vCPUs @ 2 GHz or higher 1.75 GB dedicated RAM, 2 GB for networks with greater than 15 000 NEs 1 GB available disk space 1280*1024 Display resolution for Java GUI (recommended) 1280*720@72ppi Display resolution for NFM-P applications (minimum) 1920*1080@72ppi Display resolution for NFM-P applications (recommended) | |