Support Support Downloads Knowledge Base Juniper Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[EOL/EOE] NSM - How to check and verify NSM GPG installation for license file verification.



Article ID: KB15816 KB Last Updated: 18 Oct 2020Version: 4.0
Note: A product listed in this article has either reached hardware End of Life (EOL) OR software End of Engineering (EOE).  Refer to End of Life Products & Milestones for the EOL, EOE, and End of Support (EOS) dates.
This article details steps to install GnuPG (GPG) in NSM in an attempt to correct NSM license verification issues.
Sample error printed on the console during the install for NSM license verification failure:
Enter the License File Path> /tmp/license.txt
Validating License File.....................................FAILED
Either file is not valid, or it doesn't belong to this system or you have more devices on system than license permits
NSM license is generated based on the serial number or installd ID of NSM server.   During the Installation of NSM, the user is prompted to provide the location of the license file. If the license verification fails then follow the procedure to troubleshoot the issue.

Note: The same procedure can be followed when a new license addition fails on NSM.

  1. Verify the License file using the tool /usr/netscreen/GuiSvr/utils/ as below

    /usr/netscreen/GuiSvr/utils/ verify <LICENSE_FILE_PATH>
  2. If the license verification fails with error "GPG verification failed License file is invalid" make sure the install ID or serial number listed in the file is same as the install ID or serial number of the NSM server.  Install ID can be retrieved by running the following command:
    /usr/netscreen/GuiSvr/utils/ installId
  3. Verify that the NSM server has the GPG related packages installed by running the command shown below.  If the command does not return any results, then that is an indication the GPG related libraries are missing on the NSM server.
    rpm -qa | grep gnupg
    rpm -qa | grep gpg
  4. If the GPG related libraries are missing, install the libraries by running the below command.  Follow the prompt after running the command to install the libraries.
    yum install gnupg
    yum install gpg
  5. Once GPG related libraries are installed, verify that gpg is available under /usr/bin/gpg
  6. Re-run the license verification tool.  If the verification still fails, run the below command to manually verify the license.
    /usr/bin/gpg --verify --homedir /usr/netscreen/GuiSvr/var/license/.gnupg <LICENE_FILE_PATH>
  7. If the command returns any errors, please see KB article: NSM - Debugging License Verification Issues.
Modification History:
2020-10-18: Tagged article for EOL/EOE.
Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search