Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Watch4Net | EMC M&R | ViPR SRM: How to install permanent licenses / Troubleshoot licensing issues (334741)

Last Updated: 5/29/2020Categories: TroubleshootingTotal Views: 5523Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

This article explains what to do after you have received your permanent licenses for Watch4Net/EMC M&R or ViPR SRM from the EMC licensing team through an EMC Service Request (SR). The tasks covered in this article include:

The procedure to install the Watch4Net/EMC M&R or ViPR SRM permanent license

How to add a new license file for a particular SolutionPack

How to delete a license already added to Watch4Net/EMC M&R or ViPR SRM

How to verify whether licenses that are already added to Watch4Net/EMC M&R or ViPR SRM platform are valid or expired

How to administer license files in Watch4Net/EMC M&R or ViPR SRM

What to do if licenses are not registered properly after uploading from the GUI

How to generate the Host ID for Watch4net license when upgrading from 5.2 to 6.0 (or later), without downtime.

Provide links for other knowledge articles dealing with licensing errors.

Licenses not properly registered

Cannot access the GUI due to expired licenses

Resolution

Whether you are installing permanent licensing or adding a new license file for a particular SolutionPack, the following must be done before you begin the tasks described in this article:

Obtain the required license file from the EMC licensing team through a Service Request (SR) created on the EMC Online Support site.

Make sure you have a login with root, APG, or system administrator privileges to perform the following tasks. The user apg is the account that the Watch4Net/EMC M&R or ViPR SRM application uses instead of root.

Note: This article uses examples from the Watch4Net/EMC M&R interface, but the following procedures also apply to the ViPR SRM product and interface.

Procedure to install licenses via CLI:
To install licenses, enter the following command for your operating system from the bin directory:

Operating system:                Command:
UNIX/Linux                               ./manage-licenses.sh install <download_path>/<license.zip>
Windows                                 manage-licenses.cmd install <download_path>\<license.zip>

Linux example:

./manage-licenses.sh install /opt/APG/licenses/license.zip
Windows example:
manage-licenses.cmd install /opt/APG/licenses/license.zip

Procedure to add licenses:
You must upload a license file whenever you install a new SolutionPack or ReportPack to enable views and reports to display. This can be done as follows:

Navigate to the user interface URL and log in with administrator credentials. In a default installation, the URL structure will be as follows:

http://<Frontend-hostname>:58080/APG

Click Administration.

In the Centralized Management pane, select Licenses as highlighted below:

A new window will open with Licenses Management selected.

In the Licenses Listing pane, click Upload:

In the License Upload dialog box, browse to your license file and click OK. Licenses in a .zip file are then extracted and appear in the Licenses Listing pane.

When "License Upload Complete" appears, click OK, then Continue.

IMPORTANT! If you have remote servers in a distributed environment, click Synchronize to add the licenses to the remote servers.

Procedure to delete licenses
You can select and delete specific licenses or delete all existing licenses from the server as follows:

Navigate to the user interface URL and log in with administrator credentials. In a default installation, the URL structure will be as follows:

http://<Frontend-hostname>:58080/APG

Click Administration.

In the Centralized Management pane, select Licenses.

In the Physical Overview tree, select Licenses Management.

In the Licenses Listing pane, select one or more license check boxes.

Click Delete to delete the selected licenses:

IMPORTANT! If you have remote servers in a distributed environment, click Synchronize to remove the licenses from the remote servers.

Procedure for verifying expiration status of licenses from GUI
You can verify whether licenses are valid or expired for all servers in your environment from Centralized Management. The local and remote servers listed in this view are registered with Centralized Management. This can be done as follows:

Navigate to the user interface URL and log in with administrator credentials. In a default installation, the URL structure will be as follows:

http://<Frontend-hostname>:58080/APG

Select Licenses Management.

In the Licenses Listing pane, read the Expiration column:

Procedure for verifying expiration status of licenses from CLI:

1. Open a CLI to the frontend server.
2. Navigate to <install dir>/bin

Default install directory is /opt/apg/

3. Run the following command:

Windows: manage-licenses.cmd check
Linux: ./manage-licenses.sh check

What to do if licenses have expired and uploading new licenses does not clear the error:

Navigate to the user interface URL and log in with administrator credentials. In a default installation, the URL structure will be as follows:

http://<Frontend-hostname>:58080/APG

Click Administration.

In the Centralized Management pane, select Licenses

Delete all licenses except for the Web Portal license.

Upload the new licenses.

Log out and back in to verify the proper licenses are installed.

*If the licenses still have not registered you may need to restart tomcat.

To restart tomcat

1. Open a CLI to the Front End server.

2. Navigate to <install dir>/bin.

3. Run the command

Linux: ./manage-modules.sh service restart tomcat Default

Windows: manage-modules.cmd service restart tomcat Default

How to generate the Host ID for Watch4net license when upgrading from 5.2 to 6.0 (or later), without downtime.

When upgrading Watch4Net from version 5.2 to 6.0 (or later), a host ID is required to request a new permanent license. This new Host ID can only be generated once the License-Manager has been upgraded to Watch4net 6.x, but upgrading all modules to 6.x will stop them working, as 6.x modules will not work on a 5.2 license
After updating the Watch4net Module-Manager to the new 6.x version, the License-Manager can also be upgraded to version 6.x, and all the older modules will continue to work. This will give time to request the new license files using the Host ID.

IMPORTANT! When upgrading the License-Manager, DO NOT remove the old licenses. You will be prompted to perform cleanup on old license storage as shown in the following screenshot. When prompted, select no (n) as shown below:

To upgrade the License-Manager without downtime, do the following:

When updating the License-Manager, copy the host-id string provided during the module upgrade, or execute the following command after the upgrade:

/opt/APG/bin/manage-licenses.sh host-id

Raise a Service Request to the support team so new licenses can be granted based on that host-id. Temporary licenses can be granted without a host-id if needed.

When you receive the .lic files, install them on the server. The compatibility is kept, so 5.2 modules will work with a 6.0 license (but not the opposite).

Verify that the licenses are valid.

Licensed modules are now ready to be upgraded.

Related Information

These are additional articles that deal with licensing errors:

What to do if you cannot log in due to expired web portal licenses found here.
What to do if you have device limit errors found here and here
What to do if you are unable to upload or install license keys found here.
What to di if Error in GUI: Backend Adapter (DB): unexpected failure found in Catalina log found here.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - Watch4Net/M&R

VMware Smart Assurance - SMARTS

Take Our Survey

Support Assistant