IT Operations Management (ITOM)
Showing results for 
Search instead for 
Do you mean 

How to deploy Network Performance Server within NNMi

MichaelProcopio on ‎07-08-2015 01:32 PM

Guest post by Mahipal Reddy Moola,

 

The Network Performance Server (NPS) extends Network Node Manager i’s (NNMi) functionality by providing a platform for performance data storage, analysis and reporting. NPS is the reporting tool used by NNMi Premium and NNMi Ultimate products.

 

Architecture

NPS has the following three main components:

  • ETL Server (ETL) – responsible for extracting, transforming and loading the data from NNMi data files into NPS database.
  • User Interface and Business Intelligence Server (UiBi) – responsible for storing the NPS Reports and rendering available data into reports. Built around IBM Cognos.
  • Database Server (DB) - responsible for storing performance data. Built around SAP Sybase IQ.

Supported OS

NPS 10.00 installation is supported on below platforms:

  • Windows 2008 R2 SP1
  • RHEL 6.x
  • SUSE 11 SP3

Deployment modes

NPS supports following deployment scenarios:

  • Collocated deployment mode
  • Non-collocated or Dedicated Server mode
  • Flexible Server Deployment mode - introduced in version 10.00

The following section describes each of these deployment scenarios that will help you to choose the right deployment scenario for your needs.

 

Collocated or Same Server Deployment:

 

 

In this mode NNMi and NPS are installed on the same machine (physical machine is recommended). This mode represents the basic mode of deployment and is recommended when NPS Component and Interface objects in network are less than 50K each.

 

When deployed in this mode, as NNMi and NPS will be on same server, NPS will be able access the shared data folder without any further need for sharing.

 

This mode supports HA configuration.

 

Refer to NNM iSPI Performance for Metrics install guide [Login and SAID required] for install instructions.

 

 

 

 

 

 

Non-collocated or Dedicated Server Deployment

 

 

In this mode, NNMi is installed on one machine and NPS is installed on another machine. This deployment mode most widely used deployment in production and is recommended when NPS Component and Interface objects in network are less than 400K each.

 

As NNMi and NPS are on different servers, a shared folder has to be created on NNMi server to be accessible for the NPS Server. This share can be of NFS or CIFS based on the Operating system on which NNMi and NPS are installed.

 

This mode supports HA configuration.

 

Refer to NNM iSPI Performance for Metrics install guide for install instructions.

 

Distributed or Multi-Server Deployment

 

 

The distributed deployment of NPS enables you to distribute the computing load across multiple systems and designate each system to perform a specific operation determined by the role assigned to the system and provides way to get past resource constraints on a single server.

 

In this mode NNMi is installed on one machine and NPS is further installed on multiple servers by having each of the building blocks (DB, UiBi and ETL) on a different server or one can also combine the roles depending on the load. Based on the load one can also have more than one ETL server, but can have only one DB and one UiBi server.

 

In this deployment mode, it is recommended that, NNMI share created should be of CIFS type.

 

This mode does NOT support HA configuration.

 

Refer to NNM iSPI Performance for Metrics Deployment reference guide for install instruction.

It is recommended to deploy NPS in Distributed or Multi-Server mode when the NPS Component and Interface objects in the network are 400K each or more. It is observed that the performance of NPS is better on Linux compared to Windows hence it is recommended to have NPS installed on Linux in a high scale deployment.

 

When to consider migrating one or more NPS roles to a separate machine?

 

 

Migrate to a separate ETL if:

  1. One or more Extension Packs routinely fails to complete loading within its polling interval (typically five minutes). In this case, moving the ETL role to a one or more separate machines is the recommended migration. You can analyze the performance of the Extension Packs by running the "ETL Performance by Ext. Pack" report in the Self Diagnostics folder.
  2. The number of backlogged metric dump files on NNMi shared directory are always increasing and NPS cannot process all the files.
  3. An issue persists even after moving to a separate ETL server, then consider distributing the Extension Packs among different ETL server.

Migrate to a separate UiBi server if:

  1. Users experience delays in the Navigation Panel, or the Options Panel. In this case, moving the UI/BI role to a separate machine is the recommended migration.
  2. Scheduled Reports do not complete by the desired time. In this case, moving the UI/BI role to a separate machine is the recommended migration.

Migrate to a separate DB server if:

  1. multiple extension packs are writing to DB continuously and at the same time large number of reports are being run.

To summarize

  1. If NNMi and NPS are needed at small scale and does not have much data to be processed, then one can go for Collocated/Same Server deployment.
  2. If NNMi and NPS are needed at medium or large and have to large data to be processed, then one can go for Non-collocated/Dedicated Server deployment.
  3. If one has heavy data processing (very large scale) to be done where a single NPS server cannot handle, then one go for Flexible Scale/Multi Server deployment. Further if there are multiple extension packs dumping large amounts of data, one can go for Flexible scale deployment with multiple ETL servers.
  4. It is observed that the performance of NPS is better on Linux compared to Windows hence it is recommended to have NPS installed on Linux in a high scale deployment.

 

 

About the author: Mahipal Reddy Moola has been in the HP NMC team for over 3 years with experience in testing different products in the NMC portfolio like NNMi and different Performance iSPIs. He is presently with the NNM iSPI performance for Metrics team.

 

Mahipal has B.Tech degree in Electronics and Communication Engineering from JNT University Hyderabad, India.

 

 

 

 

 

Network Node Manager i (NNMi) unifies fault, availability, and performance monitoring for your network. NNMi software helps you improve network uptime and performance, and increase responsiveness to business needs. Start your free trial today!

 

Tweet to us at @HPITOps  and let us know what you think! | Friend HP Software on Facebook   | Join our Network Management Solutions group on LinkedIn.

 

About the Author

MichaelProcopio

HPE Software Product Marketing. Over 20 years in network and systems management.

Comments
nihar
on ‎07-08-2015 09:46 PM

Great post Mahipal.. Very informative for the customers .

SaurashtraC
on ‎07-25-2015 09:13 PM

 

Hi Mahipal,

 

Mainstream support for Windows 2008 R2 has already ended. Can you please tell us, by when NNMi will start supporting Windows 2012 Operating System?

Moolam
on ‎07-26-2015 07:09 PM

Hi SaurashtraC

 

   NNMi and QASPI already supports Windows 2012.

Traffic SPI will support Windows 2012 from next release onwards

NPS will be supporting Windows 2012 R2 from next coming release (NPS cannot support Windows 2012 as one of the underlying component doesnt support Windows 2012. SO NPS will be supported on Windows 2012 R2 but not Windows 2012)

 

Mahipal.

Events
June 6 - 8, 2017
Las Vegas, Nevada
Discover 2017 Las Vegas
Join us for HPE Discover 2017 in Las Vegas. The event will be held at the Venetian | Palazzo from June 6-8, 2017.
Read more
Apr 18, 2017
Houston, TX
HPE Tech Days - 2017
Follow a group of tech bloggers for a new HPE Tech Day, a full day of sessions about how to create a hybrid IT, from hyperconverged to Composable Infr...
Read more
View all
//Add this to "OnDomLoad" event