KEMP 360 Vision

 

Introduction

KEMP 360 Vision is a proactive application delivery monitoring and visibility service provided by KEMP to help customers optimize their application Infrastructure. The KEMP LoadMaster Application Delivery Controller (ADC) is ideally placed in a network to provide an optimal view of application state. Metrics such as traffic load, server health, system throughput, concurrent connections, interface statistics, load distribution and system resource utilisation provide the information needed to determine the health of application delivery.

Along with current application state, historical metrics provide valuable information in both evaluating the long-term health of application delivery, as well as optimization and capacity planning.

KEMP 360 Vision utilises metrics collected to enable proactive health-monitoring, customer alerts, data reporting, capacity planning and configuration optimization. KEMP 360 Vision takes customer support to a new level by proving 24x7x365 active monitoring of the customer’s ADC and proactively informing customers of potential application delivery issues. In the event of an application delivery issue, the customer will be notified by your chosen method, or methods, (by phone, email and/or SMS and a KEMP support engineer will be engaged for assistance. This ensures minimum time to resolution and this proactive approach allows a large proportion of issues to be resolved before any potential service outages or user impacts occur.

Document Purpose

The purpose of this document is to provide step-by-step instructions on how to install and deploy KEMP 360 Vision.

Intended Audience

This document is of relevance to application owners as well as network and platform specialists responsible for application delivery.

Requirements

Requirements needed in order to enable KEMP 360 Vision are below:

The KEMP 360 Vision Monitor must be deployed. The KEMP 360 Vision Monitor is a virtual appliance which should be deployed on the Hyper-V or VMware hypervisor. Follow the steps in Deploy a KEMP 360 Vision Virtual Machine for instructions on how to do this.

In order to support KEMP 360 Vision, the KEMP 360 Vision Monitor requires a publicly routable IP address.

SNMP access to the LoadMaster must be enabled for the KEMP 360 Vision Monitor. Follow the steps in Configure the SNMP Options for instructions on how to do this.

HTTP, HTTPS and SSH access should be allowed from the KEMP 360 Vision Monitor to the LoadMaster.

Outbound connectivity on HTTPS (TCP Port 443) and Configuration Management (TCP Port 5367) to the KEMP Technologies Monitoring Center.

It is assumed that any LoadMasters to be monitored using KEMP 360 Vision are already set up and configured. For further details on installing and configuring a LoadMaster, please refer to the KEMP documentation page: www.kemptechnologies.com/documentation.

Each LoadMaster, High Availability (HA) pair and cloud pair must have a separate license and license key, for example – if you want to monitor three pairs of HA LoadMasters, each pair must have a license and license key

The diagram above illustrates the KEMP 360 Vision infrastructure, including firewall requirements for SSH and ICMP.

Security

All status updates are performed over a secured HTTPS connection to the KEMP Monitoring Center. In addition to this, the KEMP 360 Vision Monitor is regularly maintained and audited to ensure that the latest security protections are in place.

Install KEMP 360 Vision

Deploy a KEMP 360 Vision Virtual Machine

At present, KEMP 360 Vision can be deployed using VMware vSphere or Microsoft Hyper-V. Refer to the relevant section below for deployment instructions.

Deploy a KEMP 360 Vision Virtual Machine in VMware vSphere

To deploy the KEMP 360 Vision instance, initiate the Deploy OVF Template wizard which gathers all the information required to correctly deploy the KEMP 360 Vision instance:

  1. Open the VMware vSphere client.
  2. Select the correct Resource Pool within which you wish to install the KEMP 360 Vision instance.
  3. Select the File > Deploy OVF Template menu option. This initiates the Deploy OVF Template wizard.

  1. Within the Source screen, click the Browse button and select the OVF file.
  2. Click the Next button.

  1. Within the OVF Template Details screen, ensure that all the details regarding the KEMP 360 Vision instance are correct.
  2. Click the Next button.

  1. In the Name and Location screen, enter a name for the KEMP 360 Vision instance into the Name field.

The name can be up to 80 characters long. It should be unique within the virtual machine folder. Names are case sensitive.

  1. If required, select the folder location within the inventory where KEMP 360 Vision will reside.
  2. Click Next.
  3. Within the Resource Pool screen, select the resource pool where KEMP 360 Vision will run.

This page only displays if the cluster contains a resource pool and if you have not selected a resource pool within the inventory tree before initiating the deployment wizard.

  1. Click the Next button.

  1. Within the Storage screen, select the datastore in which you wish to store the VLM.

You may only select from preconfigured datastores within this screen.

  1. Click the Next button.

  1. Within the Disk Format screen, select whether you wish to use Thick Provision Lazy Zeroed, Thick Provision Eager Zeroed or Thin Provision.
  2. Click the Next button.

  1. Within the Network Mapping screen, select which networks in the inventory should be used for KEMP 360 Vision.
  2. Select the network mapping by choosing the relevant preconfigured network from the Destination Network drop-down list.
  3. Click Next.

  1. Within the Ready to Complete screen, ensure that all the details are correct.
  2. Click the Finish button.

Once the Finish button is clicked, the KEMP 360 Vision machine is deployed. A success message will be displayed if the deployment completes successfully.

Power on the KEMP 360 Vision Instance (in vSphere)

To power on the KEMP 360 Vision instance, follow the steps below:

In the left panel of the client, select the KEMP 360 Vision instance.

Click the Power on the virtual machine link.

Select the Console tab and wait for the instance to finish booting.

When the KEMP 360 Vision instance finishes booting, a screen similar to the one above appears. Log in to the console. The default username is kemp360 and the default password is 1fourall.

Enter a new password, when prompted.

Retype the password to confirm it.

The KEMP 360 Vision Configuration menu appears. Continue to configure the network settings by following the steps in Configure the Network Settings.

Deploy a KEMP 360 Vision Virtual Machine in Microsoft Hyper-V

To deploy a KEMP 360 Vision instance, follow the steps below within the Hyper-V Manager:

Click New.

Click Virtual Machine.

Enter a Name for the Virtual Machine and click Next.

Enter 2048 in the Memory text box and click Next.

Select External Interface as the Connection and click Next.

Select the Use an existing virtual hard disk option.

Click Browse.

Browse to and select the downloaded VHD file.

Click Finish.

Wait for the Virtual Machine to be deployed.

Power On the KEMP 360 Vision Instance (in Hyper-V)

Once the KEMP 360 Vision instance has been deployed it can be powered on:

Right-click the KEMP 360 Vision machine which was imported within the Virtual Machines pane.

Click Start.

The KEMP 360 Vision instance should begin to boot up.

Right-click the KEMP 360 Vision machine and select Connect to open the console window.

When the KEMP 360 Vision instance finishes booting, a screen similar to the one above appears. Log in to the console. The default username is kemp360 and the default password is 1fourall.

Enter a new password, when prompted.

Retype the password to confirm it.

The KEMP 360 Vision Configuration menu appears. Continue to configure the network settings by following the steps in Configure the Network Settings.

Configure the Network Settings

This section shows you how to manually configure the KEMP 360 Vision network settings, without using DHCP.

To quickly set up your KEMP 360 Vision, follow the steps below in the console:

  1. Select the Quick setup option.

  1. Press OK to continue.

  1. Select either Yes or No depending on whether you want to use DHCP or not.If Yes is selected, the network settings should be automatically configured using DHCP.If No is selected, or if DHCP does not work, continue following the steps below to manually configure the settings.
  2. On the DHCP dialog box, select No to not use DHCP.

  1. Enter the IP address and Classless Inter-Domain Routing (CIDR) you wish to assign to KEMP 360 Vision and press OK.

  1. Enter the IP address of the default gateway and press OK.

  1. Enter a, space-separated, list of name server IP addresses and press OK.

  1. Press Yes on the Reboot screen, to activate the setup.

Configure KEMP 360 Vision

A number of steps need to be performed in order to configure KEMP 360 Vision. Refer to the sections below for step-by-step instructions.

Add a Device/Cluster

To add a device or cluster to KEMP 360 Vision, follow the steps below:

Access the KEMP 360 Vision User Interface (UI) by entering the IP address, preceded by https://, in the address bar of a web browser. This is the IP address which was configured in Configure the Network Settings.

Proceed through any certificate warnings that appear.

Enter the Username and Password and click LOGIN.

Click ADD and select the relevant type to be added:

SINGLE: A single (non-HA LoadMaster)

HA PAIR: A HA pair of LoadMasters which are not deployed on the cloud

CLOUD PAIR: A HA pair of LoadMasters which are deployed on a cloud platform such as Amazon Web Services (AWS) or Microsoft Azure

Enter a name for the cluster.

This name is significant. The cluster names are used to distinguish different clusters during monitoring. You must provide these to KEMP Customer Support when enabling remote monitoring.

Enter the IP address, or addresses, as required.

Click SUBMIT.

Repeat the steps to add further devices/clusters as needed.

Configure the SNMP Options

In order to allow monitoring of the LoadMaster, SNMP must be enabled on the LoadMasters being monitored:

In the LoadMaster Web User Interface (WUI), go to System Configuration > Logging Options > SNMP Options.

Select the Enable SNMP check box.

Copy the Community String value.

This is set to public by default.

Paste the Community String value into the Community String text box in KEMP 360 Vision (in the Setup section).

Configure the Syslog Options

To configure the syslog settings on the LoadMaster, follow the steps below:

In the main menu of the LoadMaster Web User Interface (WUI), go to System Configuration > Logging Options > Syslog Options.

Enter the IP address of the KEMP 360 Vision instance into each of the Host text boxes.

If you already have a syslog server in use, the KEMP 360 Vision Monitor IP address can be appended to the existing addresses.

Click Change Syslog Parameters.

Select Virtual Services to be Monitored

Specify the Virtual Services to be monitored by carrying out the following steps in the Setup screen in KEMP 360 Vision:

Expand the Virtual Services section.

Tick the Virtual Services that you want to be monitored and for which you would like to receive alerts.

Click SAVE SETTINGS.

Enable Remote Access

Follow the steps below to enable remote access to KEMP 360 Vision:

Click SETTINGS in the bottom-left corner.

Click the Enable remote access toggle. Remote access is enabled in the screenshot above.

The Unique Identifier is used to identify the Vision Monitor. This should be provided by KEMP and should never be modified without KEMP approval.

Click the DOWNLOAD PUBLIC KEY button.

Contact KEMP Support who will add the public key to the list of trusted keys.

License the Cluster

To activate the KEMP 360 Vision license on an individual cluster, follow the steps below:

Click the cog to the right of the cluster and click License.

Enter the license key provided by KEMP and click SUBMIT.

Reboot KEMP 360 Vision

After deploying and configuring KEMP 360 Vision, the instance must be rebooted in order to complete the configuration and apply the settings. To do this, follow the steps below:

Log in to the console.

Select the Reboot option.

Click Yes to confirm the reboot.

Document History

Date

Change

Reason for Change

Version

Resp.

July 2016

Initial release

First release of document

1.0

LB

Sep 2016

Minor updates

Enhancements made

2.0

LB

Was this article helpful?

0 out of 0 found this helpful

Comments