2012-08-06 08:41 PM
We noticed insight balance requires guest access to collect information via a proxy.
This poses a security issue for us as virtual machine networks are completely isolated with no routing between the networks
Is there a workaround for this issue?
Which functionally will be missing with no guest access?
Are there any plans to collect information from the virtual center directly without guest access
2012-08-07 03:01 AM
Indeed and opposite to products collecting VM only through vCenter, OC Balance collects data directly from the Windows VM, allowing Balance to get VM paging, swapping, check alignement and draw end-to-end topology. Moreover, thanks to this end-to-end monitoring of the data path, Balance can apply its analytics to detect bottlenecks or rogue VM.
Without the Balance discovering and monitoring the VM, you're loosing many unique Balance features I'm afraid.
Windows VM are collected and monitored by the Balance Proxy.
Linux and Unix VM are collected and monitored by the Balance server.
The connection between the Balance Server and the Balance Proxy is through a single TCP port. What about setting up a proxy with dual network connection and appropriate filtering rules to allow only it to flow between the two networks?
2012-08-22 03:00 PM
You can open the firewall to allow access to the proxy between networks. Another solution is to add multiple network adapters to the Balance VA, and put them on each VM network, if there are not too many of them.
2012-09-02 01:43 PM
Our cloud architecture doest not include any open ports or routing between customers
It is strange that this product requires such connectivity which is completely unsuitable for public cloud deployments
Even stranger Given the fact that NetApp was one of the first storage vendors to support multi-tenant
Too bad, it does seem like a very good management and monitoring product, unlike other products on the market today...