Do I have the ability to add interfaces to Virtualizaton Manager with static routes so that it can exist on multiple networks, manage devices on multiple networks and provide the WebUI on multiple networks?
Virtualization Manager is just another virtual machine, so I don't see any reason why you couldn't add more interfaces. Basically, if you can do this with any other VM, you should be able to do this with Virtualization Manager. Although, if you want to monitor networks that are geographically distant, it is better to deploy a collector appliance at each location.
We did it a few releases ago for a while, however the admin page didn't recognize the second adapter. I would also use caution when doing full release upgrades. For us it didn't stay that way long because our VM infrastructure moved onto our routed network so there wasn't a reason to keep it multihomed.
True. All that being said though, you can make it work. Just understand the risk and keep a good snapshot before you try doing any upgrades. As with any linux system, multi-home and DNS don't mix because the linux resolver isn't per interface. So be sure to use static IP. In our case, we had a private, unrouted network for some of our infrastructure as well as a public routed network. Our goal was to have the solarwinds appliance sit on both sides of the fence so you could look at the infrastructure without having to be physically connected to that unrouted network. In the end, we just moved our VM hosts out of the private network and put better host based firewall rules in place.
Hi Byron,
OK, sorry had to look into this a bit more. It is not generally possible for you to bridge two unconnected networks with the single VMAN appliance. However, VMAN has Federated Collectors. You can think of these as Orion pollers (there are some technical differences, but the mental model works), except that we don't charge for these within the VMAN licensing scheme. You can deploy as many FC's in your environment as you need, usually one per geographic datacenter.
With that said, it would be recommended that you deploy the vApp in one network and a FC in the other. As long as it is possible to create 1 route between the networks, this should allow for monitoring of VM's on each network.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 195,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.