ova deploy via Command Center. Choose another VSA access node than primary

Hi Joerg,

Unfortunately it has to be done via the primary access node. There is no existing additional setting that can change this, currently.

All I could recommend to perhaps find a compromise is temporarily changing your primary VSA access node, deploying the OVA then switching the access node preference back to what it currently is.

I hope this helps.

Hi Jace,

Thanks for fast reply. This answers my question. We currently try your suggested way.

I think it would be cooler if I can select the “deploy” node or better if it would be possible to use Commvault IP tunnel infrastructure to deploy into harded networks.

In my Case I have a DMZ and Communication between the VSA access nodes and  Commserve works via proxy tunnel.

The primary VSA access node cannot reach the ESX servers in the DMZ and The Access Nodes in DMZ are only configured on subclient level not on instance level.  

We will find a way to solve this.

Thank you

Joerg

Hi Joerg,

That’s not an unreasonable suggestion at all, especially given your environment. I would recommend raising the feature request with your account manager, they should be able to get your suggestion to product management to be considered as a future feature.

Cheers,