KEMP 360 Vision Deployment Guide.

Before deploying KEMP 360 Vision it is recommended that you check out the requirements for the service. These can be found here.

Then to start setup go to the KEMP 360 Vision Home Page

Here you must log in with a KEMPID. The Vision Service is accessed and configured from here.

(If you cannot remember your KEMPID/Password it can be reset here.)


1.  Create a Vision Agent.

The first step to enable KEMP 360 Vision Proactive Support is to create a Vision Agent. The Vision Agent is a Virtual Machine that needs to be deployed in the Network which is being monitored (e.g. with Reachability to the 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 Agent e.g. if you have sites are different locations e.g Limerick, New York, Singapore.

The Vision Agent does not need to be configured directly once deployed, as all configuration and information can be accessed via ( The only time you may need to access the Agent would be to troubleshoot or resolve connection from Vision Agent to KEMP Vision or from the Vision Agent  to the monitored Resource(s).

In order to create the Vision Agent you will need to provide the name to identify it and also the IP addresses to use. This means once the VM is built you should be able to simply turn it on at it should be able to connect back to the Vision Cloud.

Supported Hypervisors include VmWare vSphere, HyperV and Oracle Virtual Box.

The Vision Agent will typically take about 2 minutes to create. Once Created it can then be downloaded.

The Agent will be in Zipped Format and Must be unzipped and deployed in the Network. See below Screens which you should see.






Once the Vision Agent has been created it can be downloaded. At this point, the Web Interface will wait for the Agent to be deployed and to connect back. (If the Agent will not be deployed for some time you can hit skip and perform some other configuration)

2. Agent Deployment

This part will vary depending on the Virtual Machine Type Selected. Below is an example of VmWare

After Download, the Agent should be unzipped and deployed. If the correct IP Addresses can be applied and all Firewall rules are in place as per the Requirements doc the agent should connect back to the KEMP Cloud once turned on.


3. Adding Communication Channel

After the Agent had connected back, the next thing to do is add a communication channel. This is how you will receive alerts about your ADC Infrastructure. Slack is the preferred Communication Channel but SMS and Email are also supported. below are some details on how to dd a Slack Communications channel. (For SMS or email simply enter the number/email address and save)


The Channel Name is a local identifier. After giving a name, you will be redirected to a slack page where you need to login to a Slack Channel and authorize KEMPBot to access and send alerts on the channel.

Click Authorize. The Page should now bring you back to the Setting Page.The Next thing you will need to do is point Vision at an ADC Cluster. A Cluster may be a Single Loadmaster or a HA Pair of Loadmasters

4. Adding Cluster

In order to monitor Loadmasters you must add a Cluster. A Cluster may be a single of High Availability Pair of Loadmasters.


 Below shows an example of adding a Single Loadmaster. For a High Availability Cluster, you will need to input the HA1 HA2 and Shared IP addresses.



If connectivity is correctly established you should see a notification that the configured resources (Loadmasters are reachable) See example below.


5. Enabling VS’s for Monitoring

Next, you will need to select which Applications (Virtual Services) you wish to monitor. This can be done by selecting the Cluster and clicking “Edit” in the top right of the screen.



Was this article helpful?

0 out of 0 found this helpful