1 Introduction

Kemp 360 Vision is a proactive monitoring solution that enables users to receive actionable insight into their application delivery, delivered through common communication channels such as email, SMS, and Slack. Setup is simple and can be completed in a matter of minutes resulting in increased uptime and reduction in common application delivery issues.

2 Prerequisites

2.1 License Requirements

To use Kemp 360 Vision, you must have a valid Kemp ID. Full-service functionality requires at least one Enterprise/Enterprise Plus licensed LoadMaster linked to this Kemp ID.

2.2 Network Infrastructure Requirements

To use Kemp 360 Vision, you must deploy at least one Vision Agent in your network to monitor your application delivery infrastructure. This agent reports telemetry and event analytics to the Kemp Cloud. To enable this, you must allow communication from the Vision Agent to the Kemp Cloud.

The following table shows the firewall rules required:

	From	To	Protocol/Port
Allow	Vision Agent	visiondata.kemptechnologies.com	TCP 8877
Allow	Vision Agent	visioncomms.kemptechnologies.com	HTTP(s) 443
Allow	Vision Agent	visionconnect.kemptechnologies.com	TCP 5367

The Vision Agent must also be able to access a DNS server for name resolution. This may also require a specific firewall rule to be in place.

In addition, your Vision Agent must be able to reach your monitored resources.

For LoadMaster monitoring, the Vision Agent must be able to reach the LoadMaster Application Programming Interface (API), which by default is HTTP(s) Port 443.

Note that while the IP address may change in the diagram above, the domain names will not change.

2.3 Vision Agent Virtual Machine Requirements

The Vision Agent Virtual Machine (VM) can be created for either VMware vSphere, Microsoft Hyper-V or Oracle VirtualBox. When creating the Vision Agent VM, ensure the following settings are used:

CPU	2 x Virtual Processors
Memory	4 GB RAM
Hard Disk	32 GB virtual hard disk thick provisioned

2.4 LoadMaster Requirements

The RESTful API interface must be enabled on the LoadMaster and accessible from the Vision Agent. The LoadMaster must be operating on firmware version 7.1-35 or later.

2.5 Communication Requirements

To receive notifications sent from Kemp 360 Vision, you must add at least one communications channel. These can be sent as simple notifications (SMS/email) or through a conversational interface (Slack).

3 Set Up

To set up Kemp 360 Vision, perform the following steps:

1. Navigate to the Kemp 360 Vision Home Page.

2. Sign in using your Kemp ID and Password.

If you cannot remember your Kemp ID/password, you can reset it at the Reset Your Password page.

3. Accept the end user product license agreement.

4. Create a Vision Agent to enable Kemp 360 Vision Proactive Support. The Vision Agent is a VM that must be deployed in the network being monitored (for example, with reachability to the Application Delivery Controller, ADC). The agent connects back to the Kemp Cloud and reports the status of application delivery.

A Vision Agent may be used to monitor multiple ADC clusters and Kemp 360 Vision also supports multiple agents (for example, if you have sites in different locations). The Vision Agent does not need to be configured directly after it is deployed because all configuration and management of the Vision Agent can be achieved through https://vision.kemptechnologies.com. The only time you may need to access the agent would be to troubleshoot or resolve connections from the Vision Agent to the Kemp Cloud or from the Vision Agent to the monitored resource(s).

To create the Vision Agent, you must provide a name to identify it and also the IP addresses to use (DHCP is also supported where the network the agent is being deployed on offers that service). This means that when the VM is built, you should be able to simply turn it on and it should be able to connect back to the Vision Cloud.

Supported hypervisors include VMware vSphere, Hyper-V, and Oracle Virtual Box.

The Vision Agent typically takes about 2 minutes to create. After it is created, it can be downloaded.

The agent is in zipped format and must be unzipped and deployed in the network.

After the Vision Agent is created, it can be downloaded. At this point, the web interface waits for the agent to be deployed and to connect back. (If the agent is not deployed for some time, you can click Skip and perform some other configuration).

3.1 Agent Deployment

This stage depends on the Virtual Machine type selected.

After downloading, the agent should be unzipped and deployed. If all firewall rules are in place (see the Network Infrastructure Requirements section), the agent should connect back to the Kemp Cloud once it is turned on.

3.2 Adding a Communication Channel

After the agent has connected back, you should add a communication channel. This enables alerts about your ADC infrastructure. To add a communication channel, perform the following steps:

1. Click the Communications Channel icon on the left navigation.

2. Click Add new channel.

3. Select your communication channel (for this example, we select Slack).

4. Type a Name and Nickname (optional) and click Add.

For email, type your email in the box provided and for SMS, select your country then type your number and click Add.

For Slack, the Channel Name is a local identifier. After giving a name, you will be redirected to a Slack page where you need to log in to a Slack channel and authorize KempBot to access and send alerts on the channel. Click Authorize. You are now brought back to the Settings page. You should now point Kemp 360 Vision at an ADC cluster. A cluster may be a single LoadMaster or a High Availability (HA) pair of LoadMasters.

3.3 Adding a Cluster

To monitor LoadMasters, you must add a cluster. A cluster may be a single or HA pair of LoadMasters.

To add a HA cluster, you must type the HA1, HA2, and shared IP addresses.

If connectivity is correctly established, you should see a notification that the LoadMasters are reachable.

 

3.4 Enabling Virtual Services for Monitoring

Next, you must select which applications (Virtual Services) you want to monitor. This can be done by selecting the cluster and clicking Edit in the top right of the screen.

Last Updated Date

This document was last updated on 19 February 2020.