3. Backup and restore the 5.1 instance to a new 5.1 instance and then upgrade to a new 5.5
instance.
a. Revert back to the 5.1 snapshot.
b. Backup the vPostgres database from the 5.1 instance.
c. Note the IP address, DNS settings, and Hostname of the 5.1 instance.
d. Shutdown the 5.1 instance.
e. Deploy a new 5.1 instance with the same IP address, DNS settings, and Hostname as
the 5.1 instance just shut down.
f. Restore the vPostgres database file to the new 5.1 instance.
g. Upgrade the new 5.1 instance to 5.5.
Related links
Troubleshooting software issues
on page 34
Avaya Aura
®
VMs do not recover
Condition
Avaya Aura
®
VMs may not recover successfully after a sudden and complete power outage when
systems are not able to gracefully shut down.
Cause
vCenter attempts to migrate the VMs to a different host when the power outage starts but cannot
complete the action when all hosts lose power. When the hosts are powered on again, vCenter
attempts to restart all hosts but cannot successfully reconnect the VMs to the network. This issue
impacts SMGR, AMS, CMS, and Session Manager instances. The following symptoms are found on
the Avaya Pod Fx when a power outage has occurred:
• vCenter is not able to complete the process of powering on the VM after the outage.
• An event is displayed indicating the Ethernet interfaces associated with the Avaya Aura
®
VM
will start disconnected.
• An error message is displayed if an attempt is made to manually reconnect the network
adapter.
Solution
1. Remove network adapters of affected VMs.
2. Add back network adapters of affected VMs.
3. Assign the MAC address originally used with the VM so the correct HWADDR value is
assigned to the Eth0 interface.
4. Install any necessary authentication files associated with the affected VMs.
Avaya Aura
®
VMs do not recover
October 2017
Troubleshooting the Avaya Pod Fx
™
43