License a newly deployed LoadMaster

In addition to adding existing, licensed LoadMasters to LoadMaster 360, you can also quickly license a newly deployed unlicensed LoadMaster and manage it through LoadMaster 360. First, manually deploy the LoadMaster.

You must have a pooled license attached to your Progress ID to use pooled licensing.

At present, LoadMaster 360 only supports perpetual LoadMaster licenses and pooled LoadMaster licensing. Service Provider License Agreement (SPLA) is not currently supported. If you try to license an SPLA LoadMaster using LoadMaster 360, you may get an Authentication failed error but this is because SPLA is not currently supported in LoadMaster 360.

Other types of LoadMasters, such as hardware, bare metal, and cloud LoadMasters can also be licensed and managed through LoadMaster 360.

When the new LoadMaster is powered on, do not access the LoadMaster User Interface (UI) to license the LoadMaster. Instead, get the IP address of the LoadMaster and follow the steps below to license the LoadMaster and add it to LoadMaster 360:

1. In LoadMaster 360, go to Infrastructure > Device Inventory.
2. Click Add Device > Add LoadMaster.
3. Click Activate a new LoadMaster.
4. Select the relevant Connector and click Next.
5. Select the LoadMaster type - LoadMaster Single or High Availability LoadMasters.
   Note: The High Availability LoadMasters option will only be displayed if you have the ability to add a High Availability pair (for example, if you have pooled licensing enabled).
6. If you select LoadMaster Single, follow the below steps:
   • Enter a name for the LoadMaster.
     Note: The only accepted characters for the LoadMaster name field are alphanumeric characters, dashes, underscores, and spaces.
   • Select either Local or NAT.
   • If you selected Local, enter the IPv4 address of the existing, unlicensed LoadMaster.
   • If you selected NAT, enter the Local interface IPv4 address for LoadMaster and the Public IPv4 address for LoadMaster.
   • You can optionally specify a Port.
     Note: If you do not specify a port number, the default of port 443 is assumed.

     When adding a LoadMaster that is deployed in Azure to LoadMaster 360, ensure to specify the port number, for example, 8443.

   • If you selected NAT, you can optionally enter the Public IPv4 address for Connector.
7. If you select High Availability LoadMasters, follow the below steps:
   • Enter a name for the LoadMaster HA pair.
     Note: The only accepted characters for the LoadMaster name field are alphanumeric characters, dashes, underscores, and spaces.
   • Enter the Partner shared secret.
     Note: For further details, refer to the following page: Set the Partner Shared Secret.
   • Enter the HA Network Parameters:
     • Select either Local or NAT. If you selected Local, enter the:
       • Shared IPv4 address
       • HA first IPv4 address
       • HA second IPv4 address
         Note: HA IP addresses must be unique.
     • If you selected NAT, enter the:
       • HA first internal IPv4 address
       • HA second internal IPv4 address
       • Shared public IPv4 address
       • HA first public IPv4 address
       • HA second public IPv4 address
   • You can optionally enter the Public IPv4 address for Connector.
   • You can optionally specify a Port.
     Note: If you do not specify a port number, the default of port 443 is assumed.

     When adding a LoadMaster that is deployed in Azure to LoadMaster 360, ensure to specify the port number, for example, 8443.

   • Specify a HA virtual ID. For further details on the HA virtual ID, refer to this page: HA Parameters.
8. Enter a new password in the Create password field for the bal administrator user.
   Note: The password must be at least 8 characters long.
   Note: The default administrator user on all LoadMasters is called bal.
9. Re-enter the new password in the Confirm password text box.
10. Use the Schedule enabled toggle to enable or disable backup scheduling for this LoadMaster.
11. If backup scheduling is enabled, select either Every day or Custom schedule (for example, weekdays only), and set the backup execution time.
12. Click Next.
13. LoadMaster 360 will then search for available licenses based on the Progress ID of the Owner role in LoadMaster 360 (refer to the Users page to see the Owner Progress ID).
14. Select the relevant license to apply to the LoadMaster and click Next.
    Note: The Pooled license capacity section displays how much of the capacity (from the total amount available) is currently used. When you select a license, the Pooled license capacity section also shows how much additional capacity will be taken up by the new license being applied. If you are over capacity, the bar appears in red.
    Note: Perpetual and pooled licensing options are available in LoadMaster 360. A perpetual license may be a subscription, free LoadMaster, or trial LoadMaster.
15. A number of setting changes are required on the LoadMaster to ensure it can communicate successfully with LoadMaster 360. You can click the changes link to review what changes will be made. Select the I agree to make the following changes to the LoadMaster check box to proceed with the addition. The changes that will be made to the LoadMaster include:
    • Local extended Edge Security Pack (ESP) logs are disabled (the Disable Local Extended ESP Logs check box will be enabled)
    • The Application Programming Interface (API) will be enabled (the Enable API check box will be enabled)
    • Session management will be enabled (the Enable Session Management check box will be enabled)
      Note: LoadMaster basic authentication is not supported with LoadMaster 360. Ensure that Require Basic Authentication is disabled in Certificates & Security > Admin WUI Access. If basic authentication is enabled on the LoadMaster, LoadMaster 360 will not be able to communicate with the LoadMaster.
    • The Connector IP address will be added to the list of syslog hosts (in System Configuration > Logging Options > Syslog Options)

      LoadMaster 360 will be allowed to securely transmit parsed log information to the cloud.

    • A local LoadMaster user with a prefix of lm360 is added with All Permissions enabled
    • An API key is generated to allow the Connector to communicate with the LoadMaster.
    • The LoadMaster password is set to the password value entered in LoadMaster 360 while adding the LoadMaster.
    • A Web Application Firewall (WAF) custom rule for log sampling is added. This rule gets enabled on all WAF-enabled Virtual Services in this LoadMaster.
16. Review the details and click Finish.
17. The LoadMaster will then get licensed and added to LoadMaster 360.

It takes a maximum of five minutes for the LoadMaster Status to update to Healthy (if it is healthy and reachable) in LoadMaster 360.