11-21-2018 06:52 PM
Can anyone advise if its possible to use multiple vrealize automation instances (dev instance and prod instance for example) via WAPI, connecting to a single infoblox deployment.
11-26-2018 09:44 AM
NIOS does not restrict how many connections can be used. There is a limit for how many SSL connections can be open at any given time, but multiple API/plugin connections is supported.
11-29-2018 08:27 PM
Many thanks for taking the time to reply. Perhaps some kind of an SSL trust issue caused issues then. We have recently built a dev environment of vRealize Automation and already had a production environment. When we used the installation workflow in the infoblox vRO plugin to install and register the IPAM endpoint in vRA and then added the endpoint in vRA the new instance started working as one would expect. Unfortunately the existing Infblox endpoint stopped functioning, any attempts to review External network profiles resulted om Error loading network range details. 400 (). Check the availability and version of the IPAM plugin. I tried using the Create IPAM connection vRO workflow to mend whatever issue was present and while the workflow was successfull the functionality of the Infoblox plugin with vRO/vRA was not mended.
In an architecture with several vRealize Automation instances is it recommeded to use different Infoblox appliances?
12-02-2018 11:11 AM
Are you using the same vRO instance for both the vRAinstance. In that case, I could see some things going wrong, though I haven't tested the scenario myself. This is just a hypothesis.
Some troubleshooting would be required to identify the actual cause of the issue.
I recommend opening a case with support. I believe that would be the best option.
3 weeks ago - last edited 3 weeks ago
If you are using a legacy, standalone PostgreSQL database, start that server.
2 In any order, start standalone vRealize Automation MS SQL servers.
3 In a deployment that uses load balancers with health checks, deactivate all health checks
4 Start the primary vRealize Automation appliance.
5 In the primary vRealize Automation appliance management interface, look under the Cluster
tab to check whether the system is in synchronous or asynchronous mode. A singleappliance deployment is always asynchronous.
n If the deployment is synchronous, start the remaining vRealize Automation appliances.
n If the deployment is asynchronous, go to the primary vRealize Automation appliance
management interface, and wait until the licensing service is running and REGISTERED.
Afterward, start any remaining vRealize Automation appliances.
After all appliances have started, use their management interfaces to verify that services are
running and REGISTERED.
It might take 15 or more minutes for appliances to start.
7 Start all IaaS Web nodes, and wait 5 minutes.
8 Start the primary Manager Service node, and wait 2 to 5 minutes.
9 In a distributed deployment with multiple Manager Service nodes, start secondary Manager
Service nodes, and wait 2 to 5 minutes.
On secondary machines, do not start or run the Windows service unless you are configured
for automatic Manager Service failover.
10 In any order, start the DEM Orchestrator, DEM Workers, and all vRealize Automation proxy
You do not need to wait for one startup to finish before starting another.
11 If you had to deactivate load balancer health checks, reactivate them.
12 Verify that started services are running and REGISTERED.
a In a browser, log in to the primary vRealize Automation appliance management interface.
b Click the Services tab.
c Monitor service startup progress by clicking Refresh.