Configuration has yet to be fully verified, Kemp Support will gladly assist if your VRealize traffic is not flowing as expected.
1 Introduction
VMware vRealize Orchestrator simplifies the automation of complex IT tasks and integrates with VMware vCloud Suite components to adapt and extend service delivery and operational management, effectively working with existing infrastructure, tools and processes.
1.1 Document Purpose
This section details a configuration for a specific application that has been provided by a customer but has yet to be fully tested.
This specific configuration will ensure that your VRealize servers are highly-available, scalable, and secure.
Configuration has yet to be fully verified, Kemp Support will gladly assist if your VRealize traffic is not flowing as expected.
2. Configuration Required
One Virtual Service listening port 8281.
2.1 Global Configuration
No Changes Required.
3 Virtual Service Configuration:
3.1 VRealize Orchestrator
> New Virtual Service
> Enter IP Address
> Port = 8281
> Name = VRealize Orchestrator
> Add New Virtual Service
3.2 Standard Options
> Disable Transparency
> Enable Subnet Originating Requests
> Persistence = None
> Scheduling Method = Round Robin
3.3 Real Servers
> Checker Parameter Type = HTTPS
> Port = 8281
> URL = /vco/api/dpcs/index.html
> Add New
> Enter Real Server IP Address
> Port = 8281
> Forwarding Method = NAT
If you have successfully Load Balanced your VRealize Orchestrator environment by implementing this specific configuration, please give a thumbs up or please leave a comment on a possible alteration that was required to make it function. Thank you
0 comments