Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > NPM licensing

NPM licensing

Created by Jeremy Holmes, last modified by Craig Healy on Feb 05, 2019

Views: 14,671 Votes: 3 Revisions: 14

Updated August 15, 2016

Overview

This article provides brief information on the NPM License tiers and how they are applied. 

Environment

All NPM versions

Detail

Licensing Scheme

NPM is licensed by the largest number of the following element types:

  • Nodes: include entire devices (routers, switches, servers, APs)
  • Interfaces: include switch ports, physical/virtual interfaces, VLANs, port-channel interfaces. Interface count is usually the largest.

    Unmanaged interfaces also use up a license. To prevent interfaces from consuming a license, remove them from the Orion Web Console.

  • Volumes: are equal to the logical disks you monitor

 

Example:

An Orion NPM SL2000 can monitor up to:

  • 2000 interfaces + up to 2000 nodes + up to 2000 volumes.

    NPM Upgrades must ensure matching NTA upgrade licenses are included as well.

Licensing Tiers

License Tier

Node Limit

Volume Limit

Interface Limit 

SL100

100

100

100

SL 250

250

250

250 

SL 500

500

500

500 

SL 2000

2000

2000

2000

SLX

Unlimited*

Unlimited*

Unlimited*

*With the default polling interval, one polling engine can monitor a maximum of 12,000 elements. To monitor over 12,000 elements, use additional polling engines (APEs). Each APE requires a license.

Suggested Tags:  NPM, Licensing

 

Reason for Rework or Feedback from Technical Content Review: 

Requested via email by Abdul Aziz. 

 

 

Last modified

Tags

Classifications

Public