Adding Devices

This section shows users how to add devices to Kemp 360 Central. Currently supported devices are: LoadMasters, LoadMaster HA Pairs, ECS Connection Manager, NGINX, HAProxy, AWS ELB, and F5 BIG-IP.

LoadMasters, like Kemp 360 Central itself, must be licensed to be activated. There are two ways to license a LoadMaster:

• License the LoadMaster by contacting the Kemp license server on the Internet.
• License locally using Kemp 360 Central.

You can add LoadMaster HA pairs that were created on the LoadMaster with Kemp 360 Central as one unit by adding the HA1 and HA2 pair as a shared IP address. The shared IP enables you to more effectively monitor the status and configuration of services across the LoadMaster HA pair. To successfully add a LoadMaster HA pair to Kemp 360 Central, both units must have the same username and password.

Before a device can be added to Kemp 360 Central, a network must exist. For steps on how to add a network, refer to the Network Management section.

1. Click the cloud icon on the left.

   

2. Highlight the relevant network. For example: if the device IP address is 192.168.150.10, you must add the device to the network that contains that IP address in its range (as specified by the network’s CIDR address).

   

3. Click the plus (+) icon in the bottom-left and select Add a Device.

Add Details for a LoadMaster

Use the following steps when adding the details for a pre-licensed LoadMaster:

1. Click the Plus icon at the bottom left of the screen then click Add a Device.
2. From the Device Type drop-down list, select LoadMaster.
3. Type the IP Address of the LoadMaster.

   The LoadMaster address must be within the IP address range specified for the network you selected in Step 2, or an error is returned.

   Note: If Network Address Translation (NAT) is being used between your LoadMaster and Kemp 360 Central (for example, your LoadMaster is located in a public cloud), ensure that the IP address in the device settings is the publicly accessible IP address.
4. Enter the Port number.
5. In a Microsoft Azure environment, type 8443 as the Port.

   If no port is entered, the port defaults to 443.

6. Type the Username and Password of the LoadMaster.
7. Type the Alternate WUI Access address for LoadMasters licensed using local licensing. If you do not specify a port number, it will be auto populated with the private port number.

   If using Azure, this is the DNS name that appears in the Azure Dashboard screen for Kemp 360 Central.

8. Enter a Nickname for the LoadMaster.

   If a Nickname is not entered here, the IP address of the LoadMaster will be used instead.

   Note: Nicknames can only be alphanumeric with hyphens, underscores, dots, and spaces.
9. Click Apply. A message will appear when the LoadMaster is added.

This will also be seen in the remote logs of the LoadMaster because it will not sync unless the IP address of Kemp 360 Central is public facing.

Add Details for a LoadMaster HA Pair

Before you create a LoadMaster HA pair, you must ensure the following:

• The two LoadMaster HA mode units participating in the HA pair have already been added to Kemp 360 Central as LoadMaster type devices.
• The two LoadMasters are available (up) and communicating successfully with Kemp 360 Central – their icons must be green or blue in the network tree.
• You know the IP addresses and ports of the two HA mode LoadMaster units, in addition to the shared IP address and port.
• Ensure that the credentials (username and password) are the same for both units.

After you ensure the prerequisites shown above are complete, perform the following steps to configure two HA mode LoadMasters into a LoadMaster HA pair:

1. Click the Network and Device Administration icon on the left.
2. Click the + icon on the lower left to open the Add a Device screen.
3. Enter or select the parameters shown in the table below:

   Parameter	Description
   Device Type	Select LoadMaster HA Pair.
   HA Shared IP : Port	Type the IP address and port of the HA shared IP address used by the HA LoadMasters.
   Platform	The platforms available are Hardware / Local Hypervisor, AWS Cloud and Azure Cloud.
   Nickname	(Optional) A name for the device that will appear in the network tree on the left and elsewhere in the UI. Nicknames can only be alphanumeric with hyphens, underscores, dots, and spaces.
   Username Password	The username and password for the HA configuration. This username and password combination must be defined on both LoadMasters.
   HA1 IP : Port	Select the LoadMaster configured as HA1 in the LoadMaster UI’s HA Configuration page.
   HA2 IP : Port	Select the LoadMaster configured as HA2 in the LoadMaster UI’s HA Configuration page.

4. Click Apply. The Shared IP Address (or Nickname, if you supplied one) now appears in the appropriate place in the network tree on the left, with the two HA mode LoadMasters organized underneath, as shown in the example below.

Add Details for a Third Party Device

In addition to LoadMasters, Kemp 360 Central enables you to manage third party devices, including NGINX, HAProxy, AWS-ELB and F5 BIG-IP.

The following are the steps for adding a third party device to Kemp 360 Central:

1. From the Device Type drop-down list, select the appropriate third party device.
2. The fields available on the screen vary depending on the Device Type selected (see the table below). Complete the fields as required. To view tool-tip text for a field, hover the cursor over the field.
3. When finished filling out the fields, click Apply.

Network Detail Automation

When adding a LoadMaster to Kemp 360 Central, network information is automatically added and configured. Some points about this are provided below:

• If the network does not already exist in Kemp 360 Central, it is added when the LoadMaster is added.
  • The LoadMaster is added to the network containing the specified IP address, for example, if a LoadMaster with IP address 10.10.20.20 contains the following networks:10.10.0.0/16
  • 10.11.0.0/1610.12.0.0/16The LoadMaster is added to the 10.10.0.0/16 network.
• If the primary network of the LoadMaster is altered (for example, from 10.10.10.20/16 to 10.10.10.20/24), the LoadMaster is moved into the new network.
• Networks automatically organize themselves in the appropriate hierarchy, for example, the network 10.154.0.0/16 automatically becomes a subnet of 10.0.0.0/8 and existing 10.154.n.n/24 networks become subnets of 10.154.0.0/16.
• Networks are not automatically removed if they are no longer present on attached LoadMasters.
• When you add a device with ‘All Networks’ selected in the Network drop-down, Kemp 360 Central attempts to locate the new device within the network that has the smallest IP address range that contains the specified IP address for the device. For example, you add the following network 13.0.0.0/8. If you then add a device with an IP address that is within that network range, such as 13.0.0.11, Kemp 360 Central places the device within that network. If there are two existing networks that contain the IP address specified, for example, 13.0.0.0/8 and 13.0.0.0/24, Kemp 360 Central locates the new devices under the network with the smaller IP address range (in this case, 13.0.0.0/24).