Menu
To provide NVIDIA vGPU software clients with continued access to NVIDIA vGPU software features if a singlelicense server fails, you can configure the license server for high availability. Highavailability requires two license servers in a failover configuration:. A primary license server, which is actively serving licenses to NVIDIA vGPU softwareclients.
These updates ensure that the panel remains current, updated, and relevant for years to come. On this page, you will find a list of all firmware updates for the GC3. The current one will be prominently displayed at the top here, to the right. Select the 'Download' button, and you will be on your way. Current Firmware: V3.2.4.6725.
A secondary license server, which acts as a backup for the primary licenseserverConfiguring two servers in a failover configuration increases availability because simultaneousfailure of two servers is rare. The primary and secondary license servers work together to ensurethat licenses in the enterprise remain continually available to NVIDIA vGPU softwareclients.If the primary license server fails, failover occurs and the secondary server cancontinue to serve licenses for up to the license server maintenance interval, which is sevendays. Note: To ensure that licenses in the enterprise remain continually available after failure of theprimary license server, return the primary server to service within sevendays of the failure. Furthermore, the remaining server becomes a single point of failure.Therefore, you should return the failed server to service as quickly as possible to restore highavailability support for the license server.During normal operation, the primary license server periodically updates the secondary serverwith information about the licenses that are being served to clients.
However, when the primaryserver is returned to service after a failure, it is not updated with information from thesecondary server about licenses that were served while the primary server was out of service.For more information about configuring the license server for high availability, see. You can install the NVIDIA vGPU software license server on Windows and Linux systems that meet thelicense server’s platform requirements. If you require high availability for the licenseserver, you must install the license server both on the system that you will use as theprimary license server and on the system that you will use as the secondary licenseserver.The license server requires a Java runtime environment and an Apache Tomcat server.
Beforeyou install the license server software, ensure that the required software is alreadyinstalled on each license server host machine that you are using:. On Windows, you need ensure only that the Java runtime environment is installed. TheApache Tomcat server is included in the license server installer for Windows. On Linux, you must ensure that both the Java runtime environment and the Apache Tomcatserver are installed.Also ensure that you have obtained your NVIDIA vGPU software and NVIDIA vGPU software License Server software. For more information, refer to. The hosting platform may be a physical machine, an on-premises virtualmachine (VM), or a VM on a supported cloud service. NVIDIA recommends using a hostthat is dedicated solely to running the license server.
The recommended minimum configuration is 2 CPU cores and 4 Gbytes of RAM. A high-endconfiguration of 4 or more CPU cores with 16 Gbytes of RAM is suitable for handling up to 150,000licensed clients. At least 1 Gbyte of hard drive space is required. The hosting platform must run a supported operating system. On Window platforms,.NET Framework 4.5 or later is required. The license server requires TCP port 7070 to be open in the platform’s firewall, to servelicenses to clients.
By default, the installer will automatically open this port.The license server’s management interface is web-based, and uses TCP port 8080. Themanagement interface itself does not implement access control; instead, the installer does notopen port 8080 by default, so that the management interface is only available to web browsersrunning locally on the license server host. Access to the management interface is thereforecontrolled by limiting remote access (via VNC, RDP, etc.) to the license server platform. If you are replacing an existing version of the license serverthat was configured to use HTTPS, copy the files that are necessary to re-instate theconfiguration after you install the new version.If you configured HTTPS for connections between the management interface and thelicense server, copy the SSL certificate that the license server was configured with.The installer deletes the entire contents of any existing license server installationfolder, including files that were added after the license server software was installed,such as the SSL certificate. Note:Copying an SSL certificate might corrupt it. To determine if the certificate iscorrupted, run this command:$JAVAHOME/bin/keytool -list -keystore certificate-file-name.jks -storepass certificate-passwordIf the certificate is corrupted, contact the CA that issued your certificate toobtain a new certificate.If you specified HTTPS for connections from a web browser to the license servermanagement interface, copy the Tomcat configuration file server.xmlso that you can reinstate the necessary changes to the Tomcat configuration. Theinstaller overwrites the existing server.xml file and any customconfiguration specified in the file is lost.
Unzip the license server installer and run setup.exe. Accept the EULA for the license server software and the Apache Tomcat software used tosupport the license server’s management interface. Destination Folder Selection on Windows. In the Choose Firewall Options dialog box, select the ports to beopened in the firewall.To enable remote clients to access licenses from the server and prevent remote accessto the management interface, use the default setting, which sets ports as follows:. Port 7070 is open to enable remote clients to access licenses from the server. Port 8080 is closed to ensure that the management interface is available onlythrough a web browser running locally on the license server host. If you are replacing an existing version of the license serverthat was configured to use HTTPS, copy the files that are necessary to re-instate theconfiguration after you install the new version.If you configured HTTPS for connections between the management interface and thelicense server, copy the SSL certificate that the license server was configured with.The installer deletes the entire contents of any existing license server installationfolder, including files that were added after the license server software was installed,such as the SSL certificate.
Note:Copying an SSL certificate might corrupt it. To determine if the certificate iscorrupted, run this command:$JAVAHOME/bin/keytool -list -keystore certificate-file-name.jks -storepass certificate-passwordIf the certificate is corrupted, contact the CA that issued your certificate toobtain a new certificate.If you specified HTTPS for connections from a web browser to the license servermanagement interface, copy the Tomcat configuration file server.xmlso that you can reinstate the necessary changes to the Tomcat configuration.
Theinstaller overwrites the existing server.xml file and any customconfiguration specified in the file is lost. Extract the contents of the license server zip archive.
Run the extracted setup binary. Note: Do not perform this task for upgrades from a 32-bit license server to a 64-bitlicense server. If you are replacing an existing version of the license serverthat was configured to use HTTPS, copy the files that are necessary to re-instate theconfiguration after you install the new version.If you configured HTTPS for connections between the management interface and thelicense server, copy the SSL certificate that the license server was configured with.The installer deletes the entire contents of any existing license server installationfolder, including files that were added after the license server software was installed,such as the SSL certificate. Note:Copying an SSL certificate might corrupt it. To determine if the certificate iscorrupted, run this command:$JAVAHOME/bin/keytool -list -keystore certificate-file-name.jks -storepass certificate-passwordIf the certificate is corrupted, contact the CA that issued your certificate toobtain a new certificate.If you specified HTTPS for connections from a web browser to the license servermanagement interface, copy the Tomcat configuration file server.xmlso that you can reinstate the necessary changes to the Tomcat configuration.
Note: For information about installing Oracle Java SE JRE, see the in the Oracle Help Center. Afterinstalling Oracle Java SE JRE, set the JAVAHOME environment variable to thejre folder of your Oracle Java SE JRE installation. Determine whether a version of Java is installed on your system. Note:The version of Apache Tomcat that is installed by your Linuxdistribution’s package manager depends on the OS version that you areusing.
This version might not be supported with this release of thelicense server.For example, installing tomcat8 on Ubuntu 16.04 installstomcat 8.0.32, but on Ubuntu 18.04, Apache Tomcat8.5. X is installed.If your package manager installs an unsupported version, use anothermeans to install a version that is supported with this release of thelicense server.For distributions based on Red Hat, use the yumpackage manager to install the tomcat andtomcat-webapps packages.nvidia@localhost $ sudo yum install tomcat tomcat-webapps.For distributions based on Debian, use theapt package manager to install thetomcat release package. Forexample, for Apache Tomcat 8, run:nvidia@localhost $ sudo apt install tomcat8.
After installing the packages, enable the Tomcat service for automatic startupon boot.For distributions based on Red Hat, enable the tomcatservice.nvidia@localhost $ sudo systemctl enable tomcat.service.For distributions based on Debian, enable thetomcat release service. Forexample, for Apache Tomcat 8, run:nvidia@localhost $ sudo systemctl enable tomcat8.service. Start the Tomcat service.For distributions based on Red Hat, start the tomcatservice.nvidia@localhost $ sudo systemctl start tomcat.service.For distributions based on Debian, start thetomcat release service.
Forexample, for Apache Tomcat 8, run:nvidia@localhost $ sudo systemctl start tomcat8.service. Verify that the Tomcat service is operational by opening the URLin a web browser.The home page of the default Tomcat web application should be displayed, asshown in. Apache Tomcat Server Path on Linux.
In the Choose Firewall Options dialog box, shown in, select the ports to be opened in the firewall.To enable remote clients to access licenses from the server and prevent remote accessto the management interface, use the default setting, which sets ports as follows:. Port 7070 is open to enable remote clients to access licenses from the server. Port 8080 is closed to ensure that the management interface is available onlythrough a web browser running locally on the license server host. Note: Support for installation in Linux console mode was introduced in licenseserver release 2018.06. It is not supported in earlier license server releases.
Thelicense server installer for earlier releases must be run in a graphical desktopenvironment. Installation in silent mode is not supported in anyrelease. Extract the contents of the license server ZIP archive. nvidia@localhost $ unzip NVIDIA-ls-linux- 2019.11.0.26416627.zip.
Add execute permission to the extracted setup binary file. nvidia@localhost $ chmod +x setup.bin. As root, run the extracted setup binary. If you no longer want to use Oracle Java SEJRE and are upgrading your existing installation of NVIDIA vGPU software license server,you can replace the Oracle Java SE JRE with the OpenJDK JRE. Check status of the Apache Tomcat service.For distributions based on Red Hat, check the status of thetomcat service.nvidia@localhost $ systemctl status tomcat.service.For distributions based on Debian, check the status of thetomcat release service.
Forexample, for Apache Tomcat 8, run:nvidia@localhost $ sudo systemctl status tomcat8.service. Check the status of the NVIDIA vGPU software license serverflexnetls-nvidia service. nvidia@localhost $ systemctl status flexnetls-nvidia.service. Stop the NVIDIA vGPU software license serverflexnetls-nvidia service.
nvidia@localhost $ systemctl stop flexnetls-nvidia.service. Stop the Apache Tomcat service.For distributions based on Red Hat, stop the tomcatservice.nvidia@localhost $ sudo systemctl stop tomcat.service.For distributions based on Debian, stop thetomcat release service.
Note: The default log level of the license server isERROR. If you enable failover support with the log level set toERROR, INFO level messages are not recordedin the log files and you will not be able to verify the setup as explained in.
To ensure thatyou can verify the setup, set the log level to INFO before enablingfailover support. If necessary, revert the log level to ERROR afterverifying the setup. For instructions, see.
In the license server management interface, selectConfiguration.The License Server Configuration page opens. When the license server is started, the default administrator account is createdand assigned super user role. This account is inactive until administrative security isenabled for the license server. Run the nvidialsadmin utility with the -usersand -create options.nvidialsadmin -users -create new-username new-user-password roles new-username Your choice of user name for the user that you are adding.
New-user-password Your choice of password for authenticating the user that you areadding. The password is case sensitive and must be astrong password that meets the requirements in. Roles One or more roles that determine operations allowed by the user formanaging licenses on the license server:. ROLEREAD grants the user privileges to performread-only operations on the license server, for example, toquery features, licenses, license reservations, or licenseserver status.
This role is assigned by default. ROLERESERVATIONS grants the user privileges tocreate and manage license reservations. ROLEADMIN grants the user administratorprivileges to update license server policies (local licenseserver only), create and manage other user accounts, and performother administrative tasks.You can assign multiple roles to a user by separating each rolewith the + sign, for example,ROLEREAD+ROLERESERVATIONS.This example adds the user lsmgr with the password3Nt3rl5vr and the ROLEADMIN role.nvidialsadmin -users -create lsmgr 3Nt3rl5vr ROLEADMIN. Run the nvidialsadmin utility with the -users and-edit options.nvidialsadmin -users -edit username user-password new-roles username The user name of the user whose account you are modifying. User-password The password for authenticating the user whose account you aremodifying.You must specify the password, even if you are not changingit.
To leave the password unchanged, specify the user's existingpassword. To change the password, specify a new password. Thepassword is case sensitive and must be a strong password thatmeets the requirements in.new-roles The new roles that determine operations allowed by the user for managinglicenses on the license server.Specify new roles only if you want tochange the roles for the account. To leave the user's existing rolesunchanged, do not specify any roles in the command.You can assignmultiple roles to a user by separating each role with the+ sign, for example,ROLEREAD+ROLERESERVATIONS.This example changes role of the user lsmgr to theROLERESERVATIONS role.
Because the user's existing password3Nt3rl5vr is specified, the password is not changed.nvidialsadmin -users -edit lsmgr 3Nt3rl5vr ROLERESERVATIONS. By default, the license server management interface connects to the license server overthe HTTP protocol. This connection is for communications between two processes that are runningon the same host machine. For increased security, you can specify that the license servermanagement interface connects to the license server over HTTPS.To configure HTTPS for connections between the management interface and thelicense server, follow this sequence of instructions:.You can also specify HTTPS for users' connections from a web browser to thelicense server management interface. Request an SSL certificate from a certificate authority (CA) in Java keystoreformat (not a PEM text file) and secured with a password.In the certificate, you can choose to identify the license serverhost through either its host name or its fully qualified domain name. Inyour certificate signing request (CSR) to the CA, ensure that the CommonName (CN) attribute of the CSR matches how the license server is identifiedin the certificate.
In thelicense-server-installation-folderserverlocal-configuration.yamlfile, edit the https-in section to set attributes that provideaccess to the certificate. License-server-installation-folder The folder in which the license server software is installed. The default license server installation folder is%SystemDrive%: NVIDIALicenseServer.Specifically, set the following attributes:. Enable HTTPS. The port number for incoming HTTPS requests.
The full or relative path to the SSL certificate file for the licenseserver on the license server host. The password with which the certificate is securedhttps-in:# Set to true to enable HTTPSenabled: true# HTTPS listening portport: https-port# Path to keystorekeystore-path: server-certificate-file-path# Keystore password. You can obfuscate this with java -jar flexnetls.jar -password your-password-herekeystore-password: password https-port The port number for incoming HTTPS requests, for example, 443. Server-certificate-file-path The full or relative path to the SSL certificate file forthe license server on the license server host.password The password with which the certificate is secured. If the passwordis obfuscated, specify the entire obfuscated string, including theOBF: prefix, for example,OBF:1ri71v1r1v2n1ri71shq1ri71shs1ri71v1r1v2n1ri7.
Note: To protect this password, ensure that thefile that contains the password is appropriately secured. Specifically, limit access to thefile that contains the password so that it can be read only by the user that the Tomcatprocess runs as and the administrator user on Windows or the root user on Linux.This example provides access to the SSL certificate filekeystore.jks, which is protected by an obfuscatedpassword. The port number for incoming HTTPS requests is 443.https-in:# Set to true to enable HTTPSenabled: true# HTTPS listening portport: 443# Path to keystorekeystore-path:.keystore.jks# Keystore password.
You can obfuscate this with java -jar flexnetls.jar -password your-password-herekeystore-password: OBF:1ri71v1r1v2n1ri71shq1ri71shs1ri71v1r1v2n1ri7. Restart the license server. In the /opt/flexnetls/nvidia/local-configuration.yamlfile, edit the https-in section to set attributes that provideaccess to the certificate.Specifically, set the following attributes:.
Enable HTTPS. The port number for incoming HTTPS requests. The name of the SSL certificate file for the license server onthe license server host. The password with which the certificate is securedhttps-in:# Set to true to enable HTTPSenabled: true# HTTPS listening portport: https-port# Path to keystorekeystore-path: server-certificate-file-name# Keystore password.
You can obfuscate this with java -jar flexnetls.jar -password your-password-herekeystore-password: password https-port The port number for incoming HTTPS requests, for example, 1443. Toavoid the need to run the license server from a privileged account,use a port number greater than or equal to 1024. On Linux systems,access to ports below 1024 is restricted to processes that run withroot user privileges.The default port for HTTPS requests is 443.If you use a different port, you can re-direct incoming HTTPSrequests for the default port to the port that you areusing.server-certificate-file-name The name of the SSL certificate file for the licenseserver on the license server host. Do not include the path tothis file.password The password with which the certificate is secured.
If the passwordis obfuscated, specify the entire obfuscated string, including theOBF: prefix, for example,OBF:1ri71v1r1v2n1ri71shq1ri71shs1ri71v1r1v2n1ri7. Note: To protect this password, ensure that thefile that contains the password is appropriately secured. Specifically, limit access to thefile that contains the password so that it can be read only by the user that the Tomcatprocess runs as and the administrator user on Windows or the root user on Linux.This example provides access to the SSL certificate filekeystore.jks, which is protected by an obfuscatedpassword. The port number for incoming HTTPS requests is 1443.https-in:# Set to true to enable HTTPSenabled: true# HTTPS listening portport: 1443# Path to keystorekeystore-path: keystore.jks# Keystore password. You can obfuscate this with java -jar flexnetls.jar -password your-password-herekeystore-password: OBF:1ri71v1r1v2n1ri71shq1ri71shs1ri71v1r1v2n1ri7. Restart the license server. By default, users connect from a web browser to the license servermanagement interface over the HTTP protocol.
For increased security, particularly ifthe license server is accessed over the public Internet, you can specify HTTPS forusers' connections from a web browser to the license server management interface.Specifying HTTPS for these connections involves configuring an HTTPS connector forthe Apache Tomcat server that the license server management interface uses. In the Tomcat configuration filecatalina-base/conf/server.xml, add aConnector element to define an SSL Coyote HTTP/1.1connector on a specific port, for, example, 8443. Catalina-base The base directory of the Apache Tomcat instance.
To help you manage your entitlements and licenses on theNVIDIA Licensing Portal, you can add other users as registered contacts inthe organization associated with your NVIDIA Enterprise Account. Role-based access helps secure the entitlements and licenses in yourorganization on the NVIDIA Licensing Portal. If you partition your entitlementsinto isolated segments, role-based access also provides isolation between the segments intowhich your entitlements are partitioned.
It does so by ensuring that only specific contacts inyour organization are allowed to view or perform actions on the entitlements and contacts thatare allocated to a virtual group.A role is a collection of actions or capabilities within the NVIDIA Licensing Portal. Each role has a scope that determines the context towhich the actions and capabilities of the role apply, specifically, a virtual group within anorganization or the organization itself.Every registered contact has at least one role, but can have multiple rolesif the scope of each role is a virtual group.
As a result, a contact can be a member ofmultiple virtual groups. However, roles with a virtual group scope and roles with anorganization scope are mutually exclusive. A contact that has a virtual group role cannot alsohave an organization role.To enable role-based access to an organization and virtual groups, the NVIDIA Licensing Portal provides pre-defined roles. An organization administrator has the highest level of visibilityand access within an organization. The person that created the organization's NVIDIA Enterprise Account is initially assigned the organization administratorrole.Each organization must have at least one organization administrator.Multiple organization administrators in an organization are allowed. An organization user has restricted visibility within anorganization and can access only items that are at the organization level and that have not beenassigned to a virtual group. A virtual group administrator has restricted visibility within anorganization and can access items and manage contacts only in the virtual group to which thevirtual group administrator is assigned.
A virtual group administrator is a contact that hasbeen added to the virtual group as an admin user.Each virtual group must have at least one virtual group administrator.Multiple virtual group administrators in a virtual group are allowed. A virtual group user has no visibility within an organization andcan view and access items only in a virtual group. To help you manage your entitlements and licenses on the NVIDIA Licensing Portal, you can add other users as registered contacts in theorganization associated with your NVIDIA Enterprise Account. You can also removeusers who no longer require access from your account on the NVIDIA Licensing Portal.To secure your entitlements and licenses, NVIDIA Licensing Portal provides role-based access for all registered contacts.Each role has a scope that determines whether the role applies to a virtual group within anorganization or the organization itself.
For more information, see. Virtual groups provide the means for segmenting your organization'sentitlements into partitions.
The virtual groups in an organization are isolated from each otherand from the organization. An entitlement cannot be partitioned and cannot be shared betweenpartitions. All licensed products in an entitlement are moved with the entitlement when theentitlement is added to a virtual group or returned to the organization.You are free to determine how many virtual groups among which to partitionyour entitlements and what those virtual groups represent. For example, you might create virtualgroups to partition your entitlements by location, division, product, or some combination offactors. Irrespective of how you choose to partition your entitlements among virtual groups,every virtual group isolates the entitlements assigned to it from other virtual groups.The following diagram shows the relationship between an organization, thevirtual groups in an organization, and the components of a virtual group.
Ensure that no licensed products in the entitlement that you want to remove have beenadded to a license server.This task requires the role. If you are not already logged in, log in to the NVIDIA Licensing Portal. In the left navigation pane of the NVIDIA Licensing Portaldashboard, click VIRTUAL GROUPS. Expand the list of entitlements in the virtual group that contains theentitlement that you want to remove by clicking the up arrow head adjacent tothe group.
In the list of entitlements, follow the Remove link forthe entitlement. Organization AdministratorsThe organization administrators are responsible for setting up virtual groups and managingentitlements for the entire organization. The individuals chosen to be organizationadministrators must understand the organization structure and purchasing process, so that theyare capable of routing newly purchased entitlements appropriately.To ensure that someone is always available to move newly purchased entitlements into thecorrect virtual group, consider designating at least three organizationadministrators. Organization AdministratorsThe organization administrators are responsible for setting up virtual groups and managingentitlements for the entire organization.
The individuals chosen to be organizationadministrators must have approval to view all entitlements purchased by the organization. Atleast one of the individuals chosen to be an organization administrator should be an employee ofthe organization to ensure that at least one direct employee is able to view the entireaccount.To ensure that someone is always available to move newly purchased entitlements into thecorrect virtual group, consider designating at least three organizationadministrators. Organization AdministratorsThe organization administrators are responsible for setting up virtual groups and managingentitlements for the entire organization. The individuals chosen to be organizationadministrators should be employees of the ISV who have approval to view and manage allentitlements for the organization.To ensure that someone is always available to add new virtual groups and respond to inquiriesfrom the virtual group administrators, who are customers, consider designating at leastthree organization administrators. Organization AdministratorsThe organization administrators are responsible for setting up virtual groups and managingentitlements for the entire organization.
The individuals chosen to be organizationadministrators must understand the organization structure and purchasing process, so that theyare capable of routing newly purchased entitlements appropriately.To ensure that someone is always available to move newly purchased entitlements into thecorrect virtual group, consider designating at least three organizationadministrators. In the license server log file, search for the string that indicates whether theserver has received or initiated a synchronization request. Licensed Feature Properties PropertyDescriptionFeatureAn abbreviated name for the feature.VersionThe version number associated with the feature.CountThe number of licenses for the feature that are currently installed on thelicense server. Each concurrent user of a feature normally consumes onelicense.AvailableThe number of licenses for the feature that are currently available to borrowfrom the server. This number decreases as users borrow licenses from the server, andincreases as licenses are returned.ExpiryThe date on which the right to use the licensed feature expires.
If thelicenses are perpetual use licenses, they have no expiration date. Perpetuallicenses are indicated by permanent in place of an expirationdate. Adding a License Reservation.
On the License Reservations page, clickAdd. On the Add Reservation page that opens, provide the details ofthe client for which you are creating the reservation and clickAdd. Group Name (Optional) Enter the name you want to assign to this reservation group. Client ID Enter the client’s Ethernet MAC address without spaces. Feature Name Enter the licensed feature name as listed on the Licensed FeatureUsage page, which is shown in.Version Enter the version number listed for the feature listed on theLicensed Feature Usage page.Count Set to the number of licenses that you want to reserve for the client.
After adding all reservations that you want to create, clickSubmit to commit the pending reservations to the licenseserver. If you purchase NVIDIA vGPU software licenses after evaluating the software,you can use the same license server that you created for yourevaluation licenses to serve your permanent licenses. Log in to the NVIDIA Licensing Portal with the account that youcreated for getting your evaluation licenses. Get the NVIDIA vGPU software for the licenses that you purchased.For instructions, refer to.
Add the licenses that you purchased to your license server on the NVIDIA Licensing Portal as explained in. Download your new license file as explained in. License Server Status in the Windows ServicesApplication.
On Linux, check the status of the flexnetls-nvidiaservice. nvidia@localhost $ systemctl status flexnetls-nvidia.serviceflexnetls-nvidia.service - LSB: start and stop FlexNet License ServerLoaded: loaded (/etc/rc.d/init.d/flexnetls-nvidia)Active: active (running) since Fri 2019-04-19 14:44:34 PDT; 2h 49min agoProcess: 4502 ExecStart=/etc/rc.d/init.d/flexnetls-nvidia start (code=exited, status=0/SUCCESS)CGroup: /system.slice/flexnetls-nvidia.service├─4567 java -Dbase.dir=/var/opt/flexnetls/nvidia -jar /opt/flexnet.└─4609 java -Dbase.dir=/var/opt/flexnetls/nvidia -jar /opt/flexnet. Inspect the license server log files, which are described in. Before restoring the trusted storage database from a backup, ensure that thefollowing prerequisites are met:. The JAVAHOME environment variable is set to the folder wherethe Java runtime environment is installed on the license server host. The TRUSTEDSTORAGEDIR environment variable is set to%SystemDrive%:WindowsServiceProfilesNetworkServiceflexnetlsnvidia,which is the folder that contains the trusted storage database files. Open a Command Prompt window and change to thelicense-server-installation-folderserverfolder.
License-server-installation-folder The folder in which the license server software is installed. The default license server installation folder is%SystemDrive%: NVIDIALicenseServer.For example: C: cd C: NVIDIALicenseServerserverC: NVIDIALicenseServerserver. In the Command Prompt window, run the command to restorethe database. C: NVIDIALicenseServerserver flexnetls.bat -restore-database. Before restoring the trusted storage database from a backup, ensure that thefollowing prerequisites are met:. The JAVAHOME environment variable is set to the directorywhere the Java runtime environment is installed on the license server host. The TRUSTEDSTORAGEDIR environment variable is set to/var/opt/flexnetls/nvidia/, which is the directory thatcontains the trusted storage database files.
Change to thelicense-server-installation-dir/serverdirectory. License-server-installation-dir The directory in which the license server software is installed. Thedefault license server installation directory is/opt/flexnetls/nvidia.For example: $ cd /opt/flexnetls/nvidia/server. Run the command to restore the database. $ flexnetls -restore-database. When the license server is used with security software, such as a firewall orantivirus software, issues may occur if the security software blocks certain applications orfunctionality.The following issues are examples of the kinds of issues that may occur if securitysoftware blocks certain applications or functionality:. Failure of the license server to start.
Access violation exceptions. Core dumps by the JRETo determine whether security software is causing these issues, test your licenseserver setup with the security software disabled or removed.
If disabling or removing thesecurity software resolves the issue, consider one of the following long-term fixes:. If your organization's software security policies allow, add an exception rule for thelicense server application. Otherwise, contact NVIDIA Enterprise Support for assistance in determining the root cause ofthe issue. When you contact NVIDIA Enterprise Support, provide a detailed description of thesymptoms of the issue and the exact versions of any security software that you are using on thelicense server host.
Start the license server uninstaller.You can start the license server uninstaller from Windows ControlPanel, Windows Explorer, or a CommandPrompt window.If you start the license server uninstaller from Windows ControlPanel or Windows Explorer, how it runs depends on themode in which license server software was installed. If the license server software wasinstalled in console mode, the uninstaller runs in silent mode. Otherwise, theConfigure License Server dialog box opens.To avoid the possibility of running the license server installer in silent mode, startit from a Command Prompt window.
In Windows Control Panel, open the Programs andFeatures pane, select License Server from thepublisher NVIDIA, and click Uninstall/Change. Start the license server uninstaller.
Change to the license server installation directory.The default license server installation directory is/opt/flexnetls/nvidia.nvidia@localhost $ cd /opt/flexnetls/nvidia. As root, run the Change License Server Installationcommand. nvidia@localhost $ sudo./Change License Server InstallationIf the license server software wasinstalled in console mode, the uninstaller runs in console mode. Otherwise, theConfigure License Server window opens. If the Configure License Server window opens, ensurethat the Uninstall Product option is selected and clickNext. Run the nvidialsadmin utility in a Windows or Linux commandshell from the folder that contains the nvidialsadmin.bat batch file orthe nvidialsadmin.sh shell script.The nvidialsadmin utility is contained in the folderlicense-server-installation-folder/enterprise.license-server-installation-folder The folder in which the license server software is installed.The default folders for the Windows and Linux platforms are as follows:.
Windows:%SystemDrive%: NVIDIALicenseServerenterprise. Linux: /opt/flexnetls/nvidia/enterprise. The format of the base URL of the license server is as follows: scheme:// address: port/api/ version/instances/ scheme The URL scheme, which is either http or https.address The address of the license server, which can be a fully-qualified domain name such asgridlicense1.example.com, or an IP address such as10.31.20.45.port The port number through which the nvidialsadmin utility accesses thelicence server. The default depends on whether scheme ishttp or https. For http, the default is 7070. For https, the default is 443.version The API version of the license server, for example, 1.0.The following examples show the different ways of specifying the address of the license serverin the base URL:. Fully-qualified domain name:.
IP address:. the license server base URL for the nvidialsadmin utility in one of thefollowing ways:. Globally for all nvidialsadmin commands by specifying theFLEXNETLSBASEURL environment variable. Individually in each nvidialsadmin command by setting the-server option. 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 DISCLAIMSALL IMPLIED WARRANTIES OF NONINFRINGEMENT, MERCHANTABILITY, AND FITNESS FOR APARTICULAR PURPOSE.Information furnished is believed to be accurate and reliable.
However, NVIDIACorporation assumes no responsibility for the consequences of use of suchinformation or for any infringement of patents or other rights of third partiesthat may result from its use. No license is granted by implication of otherwiseunder any patent rights of NVIDIA Corporation. Specifications mentioned in thispublication are subject to change without notice. This publication supersedesand replaces all other information previously supplied.
NVIDIA Corporationproducts are not authorized as critical components in life support devices orsystems without express written approval of NVIDIA Corporation. This NVIDIA product contains third party software that is made available undertheir respective software licenses.Apache Tomcat ( is provided under the following terms:Copyright 2015 NVIDIA CorporationLicensed under the Apache License, Version 2.0 (the 'License'); you may not use this file except in compliance with the License.You may obtain a copy of the License atUnless required by applicable law or agreed to in writing, software distributed under the License is distributed on an 'ASIS' BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific languagegoverning permissions and limitations under the License.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |