Reset Search
 

 

Article

KB44465 - Licenses suddenly become inactive for virtual appliance (PSA-V)

« Go Back

Information

 
Last Modified Date5/7/2020 12:19 AM
Synopsis
This article describes an issue where licenses suddenly become inactive for virtual appliance (PSA-V).
Problem or Goal
After a certain period of time, licenses will suddenly become inactive for virtual appliances (PSA-V).  After reviewing the event logs, the following message will appear:
major - [127.0.0.1] - Root::System()[] - 2020/05/04 XX:XX:XX - License server low-level protocol error, server=pcls.pulseone.net, 
Code = [7] :Could not connect
major - [127.0.0.1] - Root::System()[] - 2020/05/04 XX:XX:XX - Unable to connect to license download server pcls.pulseone.net
critical - [127.0.0.1] - Root::System()[] - 2020/05/04 XX:XX:XX - Unable to connect to Pulse Cloud License Server for '24' days.
critical - [127.0.0.1] - Root::System()[] - 2020/05/04 XX:XX:XX - Disabled installed licenses on the Virtual Appliance
If the virtual appliance cannot communicate to pcls.pulseone.net for more than 24 days, all license will be disable or become inactive.
Cause
This issue occurs when network connectivity to pcls.pulseone.net is blocked or not allow from the preferred network.
Solution
To resolve this problem, perform the following steps:

To resolve the issue, please perform one of the following methods:
  1. Login to admin console
  2. Navigate to System > Configuration > Licensing > Download License
User-added image
  1. Under License download setting, confirm the Preferred Network setting.  If the interface is incorrect, adjust accordingly, then click Save Changes
User-added image
4. Enter the auth. code again, Navigate to System > Configuration > Licensing > Download License

User-added image

TroubleShooting Steps:


If the problem persists, take the following steps:
  1. From the admin console, navigate to Maintenance > Troubleshooting > Tools > Commands
User-added image
  1. From the command drop-down, select NSLookup
  2. In the Query field, enter pcls.pulseone.net
  3. Confirm it is able to resolve the name to awazonaws.com.  If it is not able to resolve, check the DNS server setting to ensure the device is able to resolve pcls.pulseone.net or try a different interface for license download settings.
  4. It is recommended to allow pcls.pulseone.net:443 on firewall instead of IPs to allow PCLS communication to PCS virtual devices.
    pcls.pulseone.net is hosted in AWS cloud so the IP addresses are dynamic and keep changing.
  5. If manual host entries are created on Pulse appliance under System > Network > Hosts then ensure that IP address configured for pcls.pulseone.net are correct.
           Run nslookup for pcls.pulseone.net to get the IP addresses.
 
User-added image
Related Links
Attachment 1 
Created ByK. Kitajima

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255