Avaya AVP 7.1.3 Update VM Greyed Out

[mbinz]

Hi all,

Im in the midst of deploying and staging system for our customer. The system is AVP with CM, Utility Server, and Branch Session Manager. The AVP is at 7.1.3 which is something I wanted. The rest of the components are at 7.1.0, meaning I have to patch it.

Well, now I get all my patch file and patching sequence. I managed to patch my US and CM(LSP), through their respective webpage. Then it comes to BSM.

I am unable to login to my SMGR page, just showing ERR_CONNECTION_TIMEOUT thingy and when going through my Solution Deployment Manager (SDM), the "Update VM" button is greyed out. Be it when the VM powered on or powered off.

Just throwing out the systomps, guessing anyone has idea of what might go wrong or experienced this? Also, happily to provide more info to help you understand the current issue we having.

Thank you in advance.
Cheers,
Hanis

[mlombardi1]

Aura 7.1 requires DNS always be reachable, even during initial deployment which introduces a slew of logistical issues for installers. Customer DNS obviously isn't available when an AVP system is being staged off-site for an installation which is standard practice. If DNS is unavailable, the virtual machines will not function properly and I've seen this manifest in VMs refusing or dropping SSH sessions, web interfaces not initializing, SDM deployments hanging endlessly at the sanity check, etc.

The recommendation I've received from Avaya was to either load everything while physically on the customer network (which is ridiculous) or use 127.0.0.1 for DNS assignment during staging and then later update DNS on all servers when installed on the customer network.

I've tried the 127.0.0.1 method and didn't have luck with it. For this reason, any AVP-based Aura 7.x system I've installed has been 7.0. I've only seen 7.1 run correctly on customer VMware. No experience with 8.0 yet.