Kemp 360 Central is a centralized management, orchestration, and monitoring application that enables the administration of deployed LoadMaster instances.
Kemp 360 Central can be used to perform administrative tasks on each LoadMaster instance. This provides ease of administration because multiple devices, for example, LoadMasters, can be administered in one place, rather than accessing each device individually.
The purpose of this document is to provide step-by-step instructions on deploying Kemp 360 Central in Microsoft Azure.
This document is intended for anyone who needs more information about deploying Kemp 360 Central in Microsoft Azure.
Before you can deploy a Kemp 360 Central for Azure, you must sign up for an Azure account and have an active subscription. If you are new to Azure, you can view a helpful introductory video and sign up for an Azure account from the following webpage: https://azure.microsoft.com/en-us/get-started/
Note that since Version 1.25.2, the default minimum Virtual Machine provisioning requirements for new installs have been updated as follows:
|Resource||V1.24 and earlier firmware||V1.25.2 and later firmware|
|CPU||Two cores||Four cores|
|RAM||4 GB||8 GB|
|Disk Storage||40 GB||250 GB|
Upgrades to Version 1.25.2 and later releases will not update existing Virtual Machine resources. To modify your current Virtual Machine configuration to conform to the above minimum values, contact Kemp Support.
Follow the steps below to deploy Kemp 360 Central in Azure:
2. From the Azure Management Portal dashboard, click the New (plus) icon.
In some deployments, you may need to click Marketplace before you see the New icon.
Two options are available in the Azure marketplace. If you are using Kemp 360 Central for Metered Licensing or you are under a service provider agreement (SPLA), select the License Agreement Kemp 360 Central (SPLA/MELA) version, otherwise, select the BYOL version.
3. Type Kemp 360 Central in the Search field and click Return.
4. Select the Kemp 360 Central image to deploy.
If you do not have a license provided by Kemp for BYOL, SPLA, or Metered Licensing, the license defaults to a free, two device annual license. This free license may be upgraded at any stage to a full license.
5. Ensure you select Resource Manager then click Create.
6. Enter a Name for the Virtual Machine.
Azure uses this Name to create a resolvable DNS address in the cloudapp.net domain. Use this address to access the Kemp 360 Central appliance on Azure. The Name is used as the hostname, which is needed when connecting a LoadMaster to this Kemp 360 Central instance.
7. If you select SSD as the VM disk type, you must select an SSD enabled instance and if you select an HDD instance, you must select an HDD enabled instance.
Note that there is a cost associated with selecting SSD as the VM disk type.
8. Enter a User name.
9. Enter a Password. Note that your password must be between 12 and 72 characters long and contain the following:
One lowercase character
One special character other than - or /
The username and password described above are only used during the deployment process and will not be accessible on the running system. The Kemp 360 Central credentials are set later in the deployment process.
10. Select the relevant Subscription.
11. Select the relevant Resource group or create a new one if needed.
Resource groups enable you to monitor, control access, provision and manage billing for collections of assets that are required to run an application, or that are used by a client or company department. For an overview of resource groups and the Resource Manager, see: https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-overview
12. Select the relevant Location.
13. Click OK.
14. Select the same disk type that you specified in Step 7 above.
15. Select the relevant size and click Select. Note that the graphic is not indicative of current pricing requirements.
16. Create a new availability set if required. If you are going to be using Kemp 360 Central in a HA pair, then you must create an availability set for the pair when you create the first Kemp 360 Central. If it is a single Kemp 360 Central in standalone (non-HA) mode, then no availability set is required.
Note that the availability set of a virtual machine cannot be changed after it is created.
17. Next, configure the storage settings.
18. Select the relevant Virtual network or create one if needed.
19. Select the relevant Subnet.
20. Select the relevant Public IP address or create one if needed.
21. Select the relevant Network security group or create one if needed.
- TCP port 22 (SSH access for diagnostics)
- TCP port 443 (user interface and API)
The above entries are sufficient if all of your managed devices (LoadMasters and other Application Delivery Controller (ADCs)) have IP addresses that are all located on the same network segment as the Kemp 360 Central IP address. If, however, your configuration contains ADCs that are located on networks other than the local Kemp 360 Central network, you must add security group entries for the following:
- TCP port 514
- UDP port 514
The above entries in the security group are required to allow the non-local managed devices to send Syslog packets to Kemp 360 Central. The best practice is to create entries for specific networks, rather than allowing access across all networks (0.0.0.0/0).
Note that you will also need entries for all services on back-end servers to be able to communicate through the Azure firewall. These can be added to the security group now, or later after the services are defined.
See the Microsoft Azuredocumentation for more information on creating appropriate security group entries.
22. Set Auto-Shutdown to Off.
23. Set Monitoring to Enabled.
24. Set Manged server identity to No.
25. Click OK.
26. Click Create. After the VM is deployed, Azure displays the VM dashboard.
The creation of a VM may take a few minutes or more depending on the Azure portalâs responsiveness and other factors. Once created, the instance is automatically booted. If the instance fails boot, check the Boot Diagnostics from the VM dashboard for errors.
Now that the instance is deployed, Kemp 360 Central can be configured by connecting to its assigned IP address or FQDN on port 8443. For more information on this, including instructions on how to license Kemp 360 Central, refer to the Kemp 360 Central Feature Description on the Kemp Documentation Page.
Related documents are listed below:
This document was last updated on 19 February 2019.