Applicable to Entuity v19.0 upwards. If you are using an earlier version of Entuity, please see this article.
Entuity supports both standalone and distributed (Central License Server) licensing architectures. Entuity licensing checks:
- Entuity version. If you install a new release, you will need a new license.
- license expiry date.
- available modules and integrations.
- number of device and/or object credits available.
- whether the Entuity server machine is the expected machine.
- (for Central License Servers) how many remote servers it can support.
Entuity license files:
Entuity includes an evaluation license, entuity_home\etc\license.30day.eval.dat, which is valid for 30 days from the date of its installation. When using an evaluation license, Entuity will display the days and hours remaining until the license expires.
When you run configure, the default name and install location of a full license is entuity_home\etc\license.dat. However, the license files you receive from your Entuity representative have a unique name, e.g.:
- Standalone server license would have the format: License.Entuity.CustomerName.hostname.UniqueID.dat
- Central License Server license would have the format: License.Entuity.CustomerName.hostname.UniqueID_central_server.dat
- Remote Server license would have the format: License.Entuity.CustomerName.hostname.UniqueID_remote_server.dat
Standalone and Central License Server Licensing:
With standalone licensing, each Entuity server has its own license file. Each Entuity server's license:
- is associated to that particular machine through its host identifier.
- includes the number of license credits available to that server
- determines what modules and integrations you can enable on the server.
Standalone licensing is therefore usually most suitable:
- for relatively small sites.
- where the number of network objects managed by each Entuity server is known and stable.
- when the Entuity servers are not moved between machines.
- when communication between Entuity servers is not guaranteed, e.g. they are in different subnets and therefore the Central License Server model is not appropriate.
Central License Server licensing
With Central License Server licensing, the central license file contains all of the licensing information. Each remote server has a license that identifies their central server. This model is suitable where you have multiple Entuity servers.
Using a Central License Server allows you to allocate and reallocate licensing credits to remote servers as their requirements change. For example you may have three servers each with local licenses that support the same number of objects. These licenses may not reflect the current loading on those servers:
Example of locally managed licensing:
|Server||License File||Managed Objects|
|Entuity Server A||60,000 objects||45,000|
|Entuity Server B||60,000 objects||55,000|
|Entuity Server C||60,000 objects||25,000|
Example of distributed managed licensing:
|Server||License File||Managed Objects||Assigned Credits|
|Entuity Central Server A||180,000 objects||45,000||60,000|
|Entuity Server B||0 objects||55,000||70,000|
|Entuity Server C||0 objects||25,000||40,000|
When using a Central License Server:
- that is also a polling server, you must explicitly assign license credits to that server.
- all servers require a valid license, but only the licensing server includes credits for managing objects.
- a remote server can only accept license credits from one central licensing server.
- a central licensing server can only support the number of clients specified in its license file.
- the central licensing server regularly contacts its clients to confirm its presence and check license object usage. A remote server has a valid period, by default 7 days, during which it will run without contact from its server.
Note, Entuity recommends that you do not use a Central License Server to manage network objects or as a consolidation server. This is especially true in VMware Vmotion environments where the hosting virtual machine may change:
- for the remote servers, this does not present a licensing problem.
- for the Central License Server, its license is tied to the host identifier. If the machine changes, so does the host identifier and the server will fail.
If the Central License Server fails, its remote servers will continue to work for another seven days, which should be sufficient time to recover or rebuild a server.
Entuity license types:
- Associated Device (Associated Items) - this pool of license credits covers VM/SD/AP devices associated with a VM platform or other type of controller. Entuity supports for the following platforms and controllers:
- Cisco Meraki (including routers, switches, APs etc).
- Cisco Viptela (including devices from the vManage platform).
- VMWare ESXi (VMs).
- Microsoft HyperV (VMs).
- Oracle VM Manager (VMs).
- Amazon Web Services (VMs).
- Microsoft Azure (VMs).
- Aruba Wireless Controllers (APs).
- Cisco Wireless Controllers (APs).
- Basic Device (Basic Managed Devices) - this pool of license credits covers ping-only and basic managed devices for which Entuity conducts limited polling of device-level attributes and IP monitoring. There are two types of management for basic devices:
- Ping Only - checks for status via ICMP.
- SNMP - polls the following metrics (but does not include any port data):
- ICMP reachability % (including Down%, Unitialized% and OK%).
- Name (including Display Name).
- Polled IP address.
- MAC address.
- SNMP type.
- Full Device (Fully Managed Devices) - this pool of license credits covers all other fully-managed devices (controllers, VM platforms and hypervisors, servers and storage assets - note that all these asset types can only be managed with Full Management) not covered by Associated Device and Basic Device credits.
- Configuration Management (Configuration Management Devices)- this pool of license credits covers both Configuration Management and Configuration Monitoring, and is charged by device.
- Objects (Objects) - this pool of license credits covers the following:
- Managed ports on devices - including special ports that are not managed in the normal manner (i.e. proliferate/prole/prodigy/protean processes conducting walks of tables to find the ports on the devices), e.g. ports on Matrix switches, power-over-ethernet ports, and load balancer ports where these are not found in MIB2.
- Chargeable hypervisors - these use 50 objects plus 1 device credit. This is every hypervisor except the first one (which is included in the 1 device credit).
- UDComponents - added by enabling user defined polling that discovers objects, not just adding an attribute. UDComponents also use an associated device credit.
- Frame-relay DLCIs and ATM Vccs.
- Applications - i.e. TCP/UDP ports that have been configured for monitoring on devices using the applications dashboard.
- SurePath (Paths)- this pool of license credits covers the number of paths you can create in Entuity's SurePath functionality. SurePath is licensed per path and is offered in bundles of 20, 50, 100, 500, and 1000 paths.
Entuity also licenses individual modules and integrations.
Notes for license allocation per device:
- License credits will be attributed to the device by its managed name or IP.
- If a device is being managed by two different names/IPs, then it will be added as two nodes and use two license credits. E.g. A managed host for the in-band IP and a server for the out-of-band IP would use two credits. However, if both HW and OS are being managed through the same in-band IP, then only one credit will be used.
- You can pick and choose which objects that you want to manage under license. For example, if you have 100 VM platforms, but you only want to enable 10 of them, then you can do so.
Existing customers upgrading to v19.0:
If you are upgrading to v19.0, you will need to contact Entuity for a new product license. Please see below for the specific requirements of each new type of license credit.
- In 18.0 and earlier, associated devices were free.
- From v19.0 onwards, you will need a product license with sufficient Associated Device credits to cover your existing associated devices.
- If this is not done, any associated devices will no longer be managed going forward. Note, associated devices can never 'borrow' Basic Device or Full Device credits.
- In v18.0 and earlier, basic and ping only devices used a Full Device credit.
- From v19.0 onwards:
- Any existing basic and ping only devices will be converted to use Basic Device credits (if Basic Device credits are purchased with the new license).
- If Basic Device credits are not available, existing basic and ping only devices will continue to use (or ‘borrow’) a Full Device credit.
- If more Basic Device credits become available at a later date (e.g. by installing a new license, or by deleting/unmanaging other basic devices to free up credits), any basic or ping only devices currently ‘borrowing’ Full Device credits will be converted to use Basic Device credits, and their Full Device credits will be freed up.
- Any new basic and ping only devices added after upgrade can still use available Full Device credits, if no basic device credits are available.
Example of basic devices borrowing Full Device credits:
- You have a license of 1,000 Full Device credits, and your network has 800 devices overall.
- 550 of these devices are full devices, 250 are basic devices.
- 800 Full Device credits will be used, of which 250 are being used by basic devices. There are 200 available Full Device credits
- If you purchase 250 cheaper Basic Device credits, this will free up 250 Full Device credits.
- You will then have 550 full devices using Full Device credits, 250 basic devices using Basic Device credits, and 450 available Full Device credits.
Therefore, if you have basic or ping only devices when upgrading to v19.0, you have two options:
- Buy a new product license with the same number of Full Credits available as were used in the previous product license (i.e. with no Basic Device credits). In this case, everything will continue to work as it did before; or
- Purchase additional Basic Device credits to cover their existing basic and ping only devices (and therefore free up the equivalent number of Full Device credits). In this case, you would purchase a new product license with the same number of Full Device credits as used previously plus the additional Basic Device credits purchased.
- The Configuration Management module will be charged by device.
- If you have already purchased the Configuration Management module (or have already had it switched on), you will have unlimited license credits for Configuration Management in v19.0.
- If you are a new customer, you will need to purchase credits by device.
Assigning license credits:
When you install a server with a standalone license, the license credits are already assigned to the server and cannot be amended. If you wish amend the license credits and allocation, you will need to purchase and install a new license.
However, when you start the license server or remote server with a Central License Server, the license credits are not assigned. Using a central licensing server means you can allocate and reallocate licensing credits to remote servers as you want.
To assign license credits:
- In the Main Menu, click Administration.
- Click Multi-Server Configuration. This will open the Multi-Server Configuration page.
- Select the server to which you want to assign credits and click Licenses.
- This will open the Change [server name] license allocation window.
- Depending on the license model, enter the number of device and object license credits to assign to the server.
- Click OK to save, otherwise click Cancel.
- Note, a remote server that did not previously have a credit allocation will restart in a licensed mode. The Central License Server may temporarily report the remote server state as Down.
To deallocate license credits to a remote server:
- On the Multi-Server Configuration page, select the remote server from which you want to deallocate credits.
- Click Edit and set the number of device and object license credits to assign to the server to zero.
- Click OK to save, otherwise click Cancel.
If a remote server is unavailable, you cannot deallocate its license credits until it is available again.
If a server is permanently unavailable, e.g. when the remote server is restored from a backup to a new install, you must wait for one week until the license credit allocation becomes stale. Therefore, when possible you should deallocate license credits before move a server.
Checking the Entuity license:
There are three ways in which you can check the status of your Entuity license:
- Through the License Health page, which provides a breakdown of the license components. This page can be found by clicking System Information in the Main Menu, and then clicking on status symbol in the License column.
- Via the Discovered Assets or Auto Discovery tabs from the Asset Management page.
- By running checkLicense from the command line, which provides a detailed breakdown of the license components.
To run a detailed check on the Entuity license:
Run checkLicense from the command line to check the contents of the license file (by default license.dat), and view a breakdown of the licensable objects and their weighting.
- Log into the command line on the Entuity server.
- From the Entuity server bin directory, run checkLicense against license.dat: checkLicense -f pathname_of_license.dat
- For each policy group, checkLicense displays the objects and their license credit weighting. When an object has a license credit weight of:
- 0 - it is licensed but not charged, i.e. a free object.
- 1 (or more) - for each managed object, 1 (or more) credits are subtracted from the license credits available to the associated policy group.
To identify when a license expires:
Entuity will monitor the state of the current license. It will check for license expiry on its licensable components or shortage of available license credits. By default, for the 30 days before a license expires:
- Entuity will display a countdown to the expiry in the UI.
- Entuity raises Entuity Server License Alert events when one or more of its licensable components is approaching an expiry date. Entuity will also raise this event when one or more of its licensable components has reached its limit of managed objects. The event description details the licensable component(s) and the number of free credits. This is a system-wide event that appears in all Views.
To upgrade the Entuity license:
The Entuity license requires updating when:
- installing a new release of Entuity.
- moving Entuity to a new management server.
- changing the license credit allocation above the current maximum limit (otherwise, this allocation can be updated without updating the license).
- adding additional functionality through an upgrade or new modules.
- the current license is about to expire.
Please see this article for help and information on how to upgrade your Entuity license.