Avamar: Proxy Deployment manager support for multiple management interfaces

In environments Avamar Utility node is configured with multiple management's interfaces  ( non default configuration)  some of the proxy deployement can fails with a message:

avagent Error <7530>: Unable to register, no response from Administrator <bond0 ip>:28001 avagent.d Info: Client activation error.

This is expected behavior if the proxy does not have a route to the default interface (bond0)   In the proxy deployment log you will see the management network always default to bond0  

 

[     request.InitializeRequest#   fillInDefaults]Using mcs address <bond0 ip> 

This behavior is expected,   The primary purpose of proxy deployment is to help with the ease the setup of new environments with standard configuration.  Currently  (7.2x.7.3.0) proxy deployment  does not  support advance configuration such as:

1. Avamar  configured with multiple management interfaces
2. Deploying proxies with secondary network interfaces 
3. Static routes
4. Ipv6

If such configuration is required, the customer should manually deploy the proxy  using the traditional vsphere client deploy OVA method and manually register the proxy using an appropriate management interface for that proxy.