Customer Requirements for MELA Environments

MELA (Metered Enterprise Licensing Agreement) offers organizations a flexible and elastic way to license their KEMP application delivery resources, meeting both the variable application capacity demands and the multi-ADC environments that are emerging with extensive use of cloud services. By using this model, an organization can subscribe to a defined monthly capacity which can be distributed between unlimited on-demand ADC instances across multiple cloud and on premise environments (e.g. private OpenStack cloud + Azure Public Cloud).

In order to utilize this licensing architecture there are a number of requirements that must be met before arranging initial deployment with the Professional Services team.

Customer Requirements

Need to have a SPLA enabled KEMP ID. This is a KEMP ID enabled for specific additional functionality. Contact your account manager for further details.

Networking Requirements

  • Bi-directional communication between KEMP 360 Central and managed LoadMasters over TCP/443 (TCP/8443 for Azure/AWS)
  • Syslog traffic from LM to KEMP 360 Central over UDP/514.
  • KEMP 360 Central to have SMTP communication to a local SMTP server over TCP/25. This is optional if no notifications are required and MELA reporting is via HTTPs to ALSI (KEMP licensing & reporting services)
  • KEMP 360 Central to have access to a DNS resolver over TCP/UDP/53.
  • KEMP 360 Central to have access to our ALSI vis TCP/443.
  • LoadMaster instances may be accessed via a routable network or via a NAT device

Platform Requirements

Virtual Machine environment (Hyper-V, VMware, AWS or Azure) with capacity to host the KEMP360 Central instance (4GB, 2x CPU).

MELA-Network-Requirements.png

Was this article helpful?

0 out of 0 found this helpful

Comments