multiple vrealize automation instances

[#1]

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.

[#2]

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.

[#3]

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?

[#4]

Hi,

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.

Regards,

Sandeep

[#5]

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
except pings.
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
agents.
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.
https://vrealize-automation-appliance-FQDN:5480
b Click the Services tab.
c Monitor service startup progress by clicking Refresh.

iMessage App

[#6]

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.

[#7]

Multiple instances allow you to distribute the load across different servers, improving performance and accommodating a larger number of users and workloads. By deploying instances in a clustered configuration, you can achieve high availability and ensure that if one instance fails, another instance can take over seamlessly, minimizing downtime.                                                                                        MyCCPay Login

[#8]

"Multiple vRealize Automation instances" is a topic related to the use of multiple vRealize Automation (vRA) instances in an organization. vRA is a cloud automation platform that allows organizations to automate the delivery and management of IT services across multiple clouds and platforms.

Having multiple vRA instances can be useful for organizations that have different environments or use cases that require separate instances. For example, an organization may have a development instance and a production instance, with different configurations and access controls. Having separate instances can help to ensure that changes made in one environment do not affect the other environment.

However, managing multiple vRA instances can also be complex and require additional resources. It's important to carefully plan and design the architecture of the instances to ensure that they are properly integrated and can communicate with each other when needed.

Overall, the decision to use multiple vRA instances will depend on the specific needs and requirements of the organization. It's important to carefully consider the benefits and challenges of using multiple instances and to plan accordingly to ensure that they are effectively managed and integrated. gm global connect login

[#9]

Yes, it's possible to connect multiple vRealize Automation (vRA) instances to a single Infoblox deployment using WAPI (Web API). Infoblox's WAPI is flexible and can handle multiple integrations. You'd essentially have different endpoints or configurations in your vRA instances pointing to the same Infoblox system. Ensure that you manage IP allocations, DNS entries, and other configurations correctly to avoid conflicts between the environments. It's also a good practice to keep your dev and prod networks logically separated within Infoblox to maintain clarity.    Tell Tims Survey

[#10]

Based on the given search results, it is not clear whether it is possible to use multiple vRealize Automation instances via WAPI, connecting to a single Infoblox deployment. However, it is possible to use WAPI to integrate Infoblox with vRealize Automation and automate various tasks related to IP address management and DNS/DHCP services[1].

vRealize Automation is a cloud management platform that can be used to build and manage a multi-vendor cloud infrastructure[4]. It provides various features for automating IT tasks, including workflows, runbooks, and custom properties[6]. MyCVSHR login

SovLabs is a group that has produced a vSphere Tagging module for vRealize Automation, which allows for the super simple assignment of vSphere tags that involves no custom vRealize Orchestrator code or mucking around with fragile plug-ins or workflows of any sort[6].

In summary, while the search results do not provide a direct answer to the question of whether it is possible to use multiple vRealize Automation instances via WAPI, it is possible to use WAPI to integrate Infoblox with vRealize Automation and automate various tasks related to IP address management and DNS/DHCP services. Additionally, SovLabs has produced a vSphere Tagging module for vRealize Automation that allows for the super simple assignment of vSphere tags.

[#11]

---

@wisozkantwon25best botox wrote:

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.

---

Hi there,

It sounds like you're experiencing issues with the Infoblox endpoint in vRA after installing and registering a new IPAM endpoint using the Infoblox vRO plugin. This type of error often indicates a conflict or misconfiguration between the existing and new Infoblox endpoints. Here are some steps to help troubleshoot and resolve this issue:

Troubleshooting Steps:

1. Check Plugin Compatibility:

   • Ensure that the version of the Infoblox vRO plugin you are using is compatible with your version of vRA. Compatibility issues can often cause the type of errors you are seeing.

2. Verify Endpoint Configuration:

   • Double-check the configuration settings of both the new and existing Infoblox endpoints in vRA. Make sure there are no conflicts or incorrect settings that might be causing the issue.

3. Review Logs:

   • Check the vRO and vRA logs for any detailed error messages or warnings related to the Infoblox endpoints. This can provide more insight into what might be causing the "Error loading network range details. 400" error.

4. Endpoint Registration:

   • Re-register the existing Infoblox endpoint in vRA to ensure it is properly configured. Sometimes re-registering can resolve connectivity issues.

5. Network Profiles:

   • Review the external network profiles in vRA to ensure they are correctly configured and associated with the right Infoblox endpoint.