Kemp 360 Vision 2 Requirements
License requirements
To avail of Kemp 360 Vision, you will need a valid Kemp ID. Full-Service functionality requires at least one Enterprise/Enterprise Plus Licensed LoadMaster linked to this Kemp ID.
Network Infrastructure Requirements
To use Kemp 360 Vision, you will need to deploy at least one Vision Agent in your network to monitor your Application Delivery Infrastructure. This agent will report back network metrics to the Kemp Cloud. In order to enable this, you will need to allow communication from the Vision Agent to the Kemp Cloud.
Below is a simple a Network Diagram.
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 will also need to be able to access a DNS Server for Name Resolution. This may also require a specific Firewall rule to be in place.
As well as this your Vision Agent will need to be able to reach your monitored Resources.
For LoadMaster monitoring, the Vision Agent will need to be able to reach the LoadMaster's API interface which by default is HTTP(s) POrt 443.
Vision Agent VM Requirements
The Vision Agent Virtual Machine can be deployed on either VMware vSphere, Microsoft HyperV or Oracle VirtualBox. When creating the Vision Agent Virtual Machine please ensure the following Settings are used:
|
CPU |
2 X Virtual Processors |
|
Memory |
4 GB RAM |
|
Hard Disk |
32 GB Virtual Hard Disk Thick Provisioned |
LoadMaster Requirements
Restful API enabled on LoadMaster and accessible from Vision Agent. Firmware Version 7.1-35 or later.
Communication requirements
To receive notifications sent from Kemp 360 Vision you will need to add at least one Communications Channel. These can be Notifications (SMS/Email) or Conversational (Slack). We strongly recommend using Slack to allow two-way interaction with the Service.