NVIDIA License System FAQ

NVIDIA License System frequently asked questions (FAQ).

Q: What is NVIDIA License System (NLS)?

NVIDIA License System is a new system developed by NVIDIA for serving licenses to licensed NVIDIA enterprise software products, including NVIDIA vGPU software. Like the legacy NVIDIA vGPU software license server, it serves licenses from a pool of floating licenses that are obtained from the NVIDIA Licensing Portal. It is designed to replace the legacy NVIDIA vGPU software license server, which is approaching end of life.

Q: When will the legacy NVIDIA vGPU software license server reach end of life?

July 31, 2023.

Q: How do I migrate my licenses from the legacy NVIDIA vGPU software license server to NLS?

Refer to Migrating Licenses from a Legacy NVIDIA vGPU Software License Server in the NLS documentation, which provides checklists with links to detailed instructions.

Q: Why should I migrate to NLS?

You should migrate to NLS because the legacy NVIDIA vGPU software license server is approaching end of life.

The legacy NVIDIA vGPU software license server was deprecated in NVIDIA vGPU software 14.0 because release branch 14 is the last NVIDIA vGPU software release branch to support it. As a result, support for the legacy NVIDIA vGPU software license server might be removed in a future NVIDIA vGPU software release before the EOL date.

Q: What will happen after the EOL date if I do not migrate my licenses?

Refer to NVIDIA Virtual GPU Software License Server End of Life Notice for details.

Q: What should I do if my release of NVIDIA vGPU software doesn't support NLS?

Upgrade to a release of NVIDIA vGPU software that supports NLS. The EOL date of the legacy NVIDIA vGPU software license server was chosen to coincide with the EOL date of NVIDIA vGPU software release branch 11. This release branch is the last release branch that supports only the legacy NVIDIA vGPU software license server to reach EOL.

Q: What factors affect the choice between using a Cloud License Service (CLS) instance and a Delegated License Service (DLS) instance?

Because a CLS instance is set up in the cloud on the NVIDIA Licensing Portal, you don’t need dedicated resources and the process for configuring a CLS instance is much simpler than installing and configuring a DLS instance on a hypervisor host in your data center. If your IT department’s policies allow you to host licenses in the cloud on the NVIDIA Licensing Portal, consider using a CLS instance. If your IT department’s policies require that your licenses be hosted in your own data center, use a DLS instance.

Q: What are the connectivity requirements between a licensed client VM in a customer’s data center and a service instance? For example, are there any specific requirements for ports, URLs, or proxy configuration? Is the client traffic just HTTPS traffic or does a service instance require port 7070 to be open?

All traffic between a CLS or DLS instance and a licensed client is HTTPS traffic.

To enable communication between a licensed client and a CLS or DLS instance, the ports that must be open in your firewall or proxy depend on whether the service instance is a CLS instance or a DLS instance:

  • For a CLS instance, ports 443 and 80 must be open.
  • For DLS 1.0, ports 443, 80, 8081, and 8082 must be open.
  • For DLS 1.1 and later releases, ports 443 and 80 must be open.

If you are using an HA cluster of DLS instances with a firewall or proxy server between the DLS instances, the following ports must also be open in the firewall or proxy server:

Port Containerized Instance VM-Based Instance Protocol Egress/Ingress Protocol/Service From To
443 - TLS, TCP Both Licensing Services Primary DLS Secondary DLS
4369 EPMD (peer discovery) Both RabbitMQ, Erlang Primary DLS Secondary DLS
5671 AMQP, TLS Both RabbitMQ Primary DLS Secondary DLS
8080 HTTPS Both Licensing Services Primary DLS Secondary DLS
8081 HTTPS Both Licensing Services Primary DLS Secondary DLS
8082 HTTPS Both Licensing Services Primary DLS Secondary DLS
8083 HTTPS Both Licensing Services Primary DLS Secondary DLS
8084 HTTPS Both Licensing Services Primary DLS Secondary DLS
8085 HTTPS Both Licensing Services Primary DLS Secondary DLS
✔ Port is used.

- Port is not used.

The following ports that were required to be open in earlier releases are no longer used:
  • 22
  • 1883
  • 5672
  • 8883
  • 15672
  • 25671
  • 25672
  • 61613
  • 61614
The following ports must be available in the container orchestrator to allow the DLS appliance container to bind to them:
Port Service
8080, 18080 Administration Service
8081, 18081 Authorization Service
8082, 18082 Licensing Services
8083, 18083 File Installation
8084, 18084 Service Instance
8085 Virtual Appliance Service
9001 Process Manager (supervisord)
25672 RabbitMQ

After the client configuration token is generated and copied to the licensed client, the client uses information in the token to locate the service instance when requesting a license from the instance.

Q: Are there any additional security considerations for using a CLS instance?

No.

Q: When a client loses connection to a CLS or DLS instance, is the behaviour the same as for a legacy NVIDIA vGPU software license server?

Yes. Refer to Software Enforcement of NVIDIA vGPU Software Licensing in Virtual GPU Client Licensing User Guide for more information.

Q: Is the general enforcement of NVIDIA vGPU software licenses by a CLS or DLS instance the same as for a legacy NVIDIA vGPU software license server?

Yes. Refer to How NVIDIA vGPU Software Licensing Is Enforced in Virtual GPU Client Licensing User Guide for more information.

Q: When a master VM image is updated periodically, must the client configuration token be regenerated each time the image is updated?

No. A client configuration token is valid for 12 years after it is generated. If the client configuration token is valid when the image is updated, it does not need to be regenerated.

However, the token must be copied to any VMs that will use the token while the token is still valid. Before creating a VM from a master VM image that contains a client configuration token, ensure that the token is still valid. If the client configuration token has expired, regenerate it and copy it to the master VM image before creating a VM from the master VM image.

Any VM created from the master image checks the validity of the token. After the token is validated, it remains valid throughout the lifetime of the VM, even if the VM is rebooted.

Q: Where should a client configuration token be stored when used with a single-image technology such as Citrix MCS or PVS? Can either the default location or a shared network drive be used on the master image?

Yes, you can store the client configuration token in a shared drive or modify your MCS or PVS steps to copy the token to the default location in the master image.

Q: How do I update a DLS virtual appliance when NVIDIA has added an updated DLS virtual appliance image file to the NVIDIA Licensing Portal?

This process is described in detail in Migrating a DLS Instance in NVIDIA License System User Guide.

Q: Can I mix DLS instances and CLS instances in a production system?

Yes. You can have one set of licensed clients connected to a DLS instance and another set of licensed clients connected to a CLS instance.

You must create two different license servers on the NVIDIA Licensing Portal: One license server must be installed on the CLS instance and the other license server must be downloaded and installed on the DLS instance.

You must also generate one client configuration token for the CLS instance and another client configuration token for the DLS instance, and deploy each token on the set of clients to be connected to the instance for which you generated the token.

Q: Does the DLS virtual appliance provide an API or CLI for viewing DLS instance statistics and usage?

The DLS virtual appliance reports when CPU usage, memory usage, or disk usage exceeds 60% of the total available. These statistics can be found in the file /var/log/nls-telemetry on the DLS virtual appliance.

For more information about the log files on a DLS virtual appliance and how to access them, refer to Log File Locations and Types for a DLS Virtual Appliance in NVIDIA License System User Guide.

Q: How are DLS virtual appliances protected, and if a vulnerability is found, how will NVIDIA address it?

If a security vulnerability in the DLS virtual appliance is reported, NVIDIA aims to release a security update within 90 days of the vulnerability being reported. For a zero-day vulnerability, NVIDIA aims to release a security update as soon as possible after the vulnerability is reported.

Q: Is a DLS virtual appliance preconfigured with any user accounts?

Yes. Each DLS software image is configured with a fixed set of user accounts. You cannot add other user accounts to the software image. Furthermore, modifications to the configured accounts are strictly controlled. Each account is provided for a specific purpose.

User Account Purpose
dls_admin DLS administrator account. This account provides access through a web-based management interface to the NVIDIA Licensing application on a DLS virtual appliance. The DLS administrator user name can be changed from the preset dls_admin name.
dls_diagnostics DLS diagnostics user account. This account provides access only to the log files for a DLS virtual appliance through the hypervisor console and secure shell (SSH). This account can be enabled during the registration of the DLS administrator user. It can also be enabled and disabled by changing the dls_admin user's settings in the My Info window.
Note: This account is not available for containerized DLS software images.
dls_system DLS system user account. This account provides access to the VM that hosts a DLS virtual appliance through the hypervisor console. The dls_system user can perform only a limited number of predefined system administration tasks from the VM that is accessed through this account.
Note: This account is not available for containerized DLS software images.
rsu_admin DLS sudo user account. This user account has the elevated privileges required to update and upgrade the GPL/LGPL v3 licensed Open Source Software (OSS) libraries within the DLS virtual appliance. This account provides no other access to a DLS virtual appliance. It is provided to comply with the terms of the GPL/LGPL v3 license under which some libraries in the operating system in the DLS virtual appliance are released. For information about how to create the DLS sudo user account, refer to NVIDIA License System Release Notes.
Note: This account is not available for containerized DLS software images.

Q: As a customer, how much management of a CLS instance am I required to do? For example, can I reboot a CLS instance if I have an issue?

None. The CLS infrastructure is managed completely by NVIDIA. The NVIDIA Licensing Portal provides no interfaces for users to reboot a CLS instance.

Notices

Notice

This document is provided for information purposes only and shall not be regarded as a warranty of a certain functionality, condition, or quality of a product. NVIDIA Corporation (“NVIDIA”) makes no representations or warranties, expressed or implied, as to the accuracy or completeness of the information contained in this document and assumes no responsibility for any errors contained herein. NVIDIA shall have no liability for the consequences or use of such information or for any infringement of patents or other rights of third parties that may result from its use. This document is not a commitment to develop, release, or deliver any Material (defined below), code, or functionality.

NVIDIA reserves the right to make corrections, modifications, enhancements, improvements, and any other changes to this document, at any time without notice.

Customer should obtain the latest relevant information before placing orders and should verify that such information is current and complete.

NVIDIA products are sold subject to the NVIDIA standard terms and conditions of sale supplied at the time of order acknowledgement, unless otherwise agreed in an individual sales agreement signed by authorized representatives of NVIDIA and customer (“Terms of Sale”). NVIDIA hereby expressly objects to applying any customer general terms and conditions with regards to the purchase of the NVIDIA product referenced in this document. No contractual obligations are formed either directly or indirectly by this document.

NVIDIA products are not designed, authorized, or warranted to be suitable for use in medical, military, aircraft, space, or life support equipment, nor in applications where failure or malfunction of the NVIDIA product can reasonably be expected to result in personal injury, death, or property or environmental damage. NVIDIA accepts no liability for inclusion and/or use of NVIDIA products in such equipment or applications and therefore such inclusion and/or use is at customer’s own risk.

NVIDIA makes no representation or warranty that products based on this document will be suitable for any specified use. Testing of all parameters of each product is not necessarily performed by NVIDIA. It is customer’s sole responsibility to evaluate and determine the applicability of any information contained in this document, ensure the product is suitable and fit for the application planned by customer, and perform the necessary testing for the application in order to avoid a default of the application or the product. Weaknesses in customer’s product designs may affect the quality and reliability of the NVIDIA product and may result in additional or different conditions and/or requirements beyond those contained in this document. NVIDIA accepts no liability related to any default, damage, costs, or problem which may be based on or attributable to: (i) the use of the NVIDIA product in any manner that is contrary to this document or (ii) customer product designs.

No license, either expressed or implied, is granted under any NVIDIA patent right, copyright, or other NVIDIA intellectual property right under this document. Information published by NVIDIA regarding third-party products or services does not constitute a license from NVIDIA to use such products or services or a warranty or endorsement thereof. Use of such information may require a license from a third party under the patents or other intellectual property rights of the third party, or a license from NVIDIA under the patents or other intellectual property rights of NVIDIA.

Reproduction of information in this document is permissible only if approved in advance by NVIDIA in writing, reproduced without alteration and in full compliance with all applicable export laws and regulations, and accompanied by all associated conditions, limitations, and notices.

THIS DOCUMENT AND ALL NVIDIA DESIGN SPECIFICATIONS, REFERENCE BOARDS, FILES, DRAWINGS, DIAGNOSTICS, LISTS, AND OTHER DOCUMENTS (TOGETHER AND SEPARATELY, “MATERIALS”) ARE BEING PROVIDED “AS IS.” NVIDIA MAKES NO WARRANTIES, EXPRESSED, IMPLIED, STATUTORY, OR OTHERWISE WITH RESPECT TO THE MATERIALS, AND EXPRESSLY DISCLAIMS ALL IMPLIED WARRANTIES OF NONINFRINGEMENT, MERCHANTABILITY, AND FITNESS FOR A PARTICULAR PURPOSE. TO THE EXTENT NOT PROHIBITED BY LAW, IN NO EVENT WILL NVIDIA BE LIABLE FOR ANY DAMAGES, INCLUDING WITHOUT LIMITATION ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF ANY USE OF THIS DOCUMENT, EVEN IF NVIDIA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Notwithstanding any damages that customer might incur for any reason whatsoever, NVIDIA’s aggregate and cumulative liability towards customer for the products described herein shall be limited in accordance with the Terms of Sale for the product.

VESA DisplayPort

DisplayPort and DisplayPort Compliance Logo, DisplayPort Compliance Logo for Dual-mode Sources, and DisplayPort Compliance Logo for Active Cables are trademarks owned by the Video Electronics Standards Association in the United States and other countries.

HDMI

HDMI, the HDMI logo, and High-Definition Multimedia Interface are trademarks or registered trademarks of HDMI Licensing LLC.

OpenCL

OpenCL is a trademark of Apple Inc. used under license to the Khronos Group Inc.

Trademarks

NVIDIA, the NVIDIA logo, NVIDIA Maxwell, NVIDIA Pascal, NVIDIA Turing, NVIDIA Volta, Quadro, and Tesla are trademarks or registered trademarks of NVIDIA Corporation in the U.S. and other countries. Other company and product names may be trademarks of the respective companies with which they are associated.