Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Troubleshooting the Juniper Agile License Manager

Troubleshooting the Juniper Agile License Manager

This topic provides a general guide to troubleshooting some typical problems you might encounter.

Installation Fails for Non-Root Users

Problem

When a non-root user tries to install the Agile License Manager by invoking the following install script, an error message is displayed during the installation process.

$ ./install64.sh -S 10.221.133.158 -I ../LicenseManagerIdentity.xml --accept-agreement --force -P /opt/license -H agile-license-server-03

Solution

On Ubuntu devices use the sudo prefix to provide root access to the installation or log in as root user.

$ sudo ./install64.sh -S 10.221.133.158 -I ../LicenseManagerIdentity.xml --accept-agreement --force -P /opt/license -H nari-agile-license-server-03

Invalid or Corrupt Agile License Manager ID File

Problem

When you try to install the Agile License Manager by invoking the following install script, an error is displayed during the installation process.

$ sudo ./install64.sh -S 10.221.133.158 -I ../LicenseManagerIdentity.xml --accept-agreement --force -P /opt/license -H nari-agile-license-server-03

Solution

The issues occurs because of a corrupted or edited LicenseManagerIdentity.xml file is downloaded from the Agile Licensing Portal. The user must not edit the file. If the file is corrupted, download the file again from the portal and perform the installation.

Error Checking Status of Agile License Manager

Problem

The message Error checking...133 is seen when the .Agile License Server is started.

Solution

Issue is due to the servers configured in server group are not able resolve, either it could be local server name or other servername in the group.

Say there are blrserver01, blrserver02, blrserver03 servers in server group and only blrserver01 is being used and others are dummy server then you need to add the entries in /etc/hosts file as below. The entries are required to ensure all the hostnames are able to resolve.

Agile License Manager Starts as Follower Instead of Leader

When you start an Agile License Manager that is the LEADER (per the preference order it should start as the LEADER) by using the #sudo ./start64.sh command, it starts as FOLLOWER. The following output is displayed:

Solution

When server is started, there will be LEADER/FOLLOWER election among the servers configured in the lserv_advance_config.xml file used in the installation with -A option to denote multiple servers in the redundancy setup.

During the RMS server LEADER election, the order of preference is as per the order of the servers listed in the previous output, and whichever server is up and is running with the License Manager setup will take the LEADER role. For example, if agile-license-server-01 is down, then agile-license-server-02 will take the LEADER role. When agile-license-server-01 is back online, it will take back the LEADER role.

However, during initialization, the Agile License Manager status shown might be transient and might change after a few seconds depending on the availability of the other Agile License Managers in the group.

You can verify the Agile License Manager status by running the following command at any time when the Agile License Manager is running.

# sudo ./lsmon64 -d -l localhost