A single VMware cluster can be shared between Avaya Oceana® 3.10.x and Avaya Analytics™ 4.2.x/4.3.x.

• The cluster contains virtual machines for both Avaya Oceana® 3.10.x and Avaya Analytics™ 4.2.x/4.3.x.

• The cluster can also contain virtual machines of other applications without contention.

Yes

For instructions on enabling affinity rules in a DRS-enabled VMware cluster, see PSN005416u located at https://downloads.avaya.com/css/P8/documents/101057845.

Yes

For more information, see PSN005633u located at https://downloads.avaya.com/css/P8/documents/101067348.

Cloning

No

No

Avaya Analytics™ supports cloning cluster node VMs during the initial OVA deployment before they are powered up.

Distributed Resource Scheduler (DRS)

Yes

For the documented guidelines in conjunction with affinity rules, see PSN005416u located at https://downloads.avaya.com/css/P8/documents/101057845.

Yes

For the documented guidelines on HA and DRS rules for Avaya Analytics™ 4.x, see PSN005633u located at https://downloads.avaya.com/css/P8/documents/101067348.

Storage DRS

No

Avaya Oceana® does not support this feature. There are impacts to the datastores. The input or output load balancing occurring in production can cause outages.

No

Distributed Power Management (DPM)

No

No

Distributed Switch (Network)

Yes

• Requires VMware Enterprise Plus license.

  Note:

  Loss of vCenter indicates that you cannot manage data networks on the hosts.

• If you use standard vSwitch, you can do the management from each host.

Yes

• Requires VMware Enterprise Plus license.

  Note:

  Loss of vCenter indicates that you cannot manage the data networks on the hosts.

• If you use standard vSwitch, you can do the management from each host.

Fault Tolerance

No

No

High Availability (HA)*

No

• Avaya Oceana® does not support impacts to the virtual machines occurring in production.

• For more information on configuring VMware HA in an Avaya Oceana® and Avaya Analytics™ single cluster deployment, see PSN005633u located at https://downloads.avaya.com/css/P8/documents/101067348.

Yes

• Mandatory for Avaya Analytics™ 4.x High Availability feature.

• For the documented guidelines on HA and DRS rules for Avaya Analytics™ 4.x, see PSN005633u located at https://downloads.avaya.com/css/P8/documents/101067348.

Snapshots***

Partial

• Yes, as part of maintenance window** procedures only for upgrades or patching.

• You must remove all snapshots before putting the contact center back into production.

Partial

• Yes, as part of maintenance window** procedures for upgrades or patching only for the following Avaya Analytics™ application:

• Cluster Control Manager (CCM) - You must remove all snapshots before putting the contact center back into production.

• Snapshots are supported for all the VMs in the cluster.

Storage Thin Provisioning

Partial

• Yes, for SAN storage.

• No, for local hard disk storage.

Yes

• Yes, for SAN storage.

• No local storage supported.

  Note:

  Applicable only to Avaya Analytics™ on HA.

• For more information on specifics of thin provisioning, see Thin provisioning of disk storage in VMware.

Suspend and Resume

No

No

Cold Migration

Yes

• You can do a cold migration only on a virtual machine in a powered-off state.

• Avaya Oceana® uses static IPs. Therefore, the new ESXI host(s) must have access to the original data network and datastore for the migrated virtual machines.

Yes

• You can do cold migration only on a virtual machine in a powered-off state.

• Avaya Analytics™ uses static IPs. Therefore Avaya Analytics™ virtual machines can only be migrated to hosts in the same VMware that has the same access to all elements in the cluster as existing hosts.

When performing any cold migrations of Avaya Analytics™virtual machines from host to host, see the Considerations for upgrading Physical Hosts running Avaya Analytics™ virtual Machine section in Deploying Avaya Analytics™.

Reservations on vCPU and memory required to be enabled

Yes

• Set to Yes. For production environments, Avaya Oceana® customers provide the VMware deployments wherever there is contention for resources.

• Physical hosts running Avaya Oceana® virtual machines can have other virtual machines running and co-residing with the Avaya Oceana® virtual machines.

• On Avaya Pod Fx systems, reservations are not required, because the Avaya supplied hardware is engineered not to be over provisioned.

No

Avaya Analytics™ 4.x reservations on vCPU and memory are not mandatory, as long as the environment is not over provisioned and there is no contention for resources with other virtual machines.

Hyperthreading

No

• Avaya Oceana® requires reservations. Therefore, Hyperthreading does not add any additional value.

• You can enable on the VMware infrastructure for the other applications.

Yes

• * Avaya Oceana® provides its own HA mechanism.

• ** A maintenance window specifies a scheduled out-of-production window where the system does not process contacts, agents are all logged out, and queues are empty. This timeframe is dedicated to tasks such as patching, upgrades, and configuration.

  • During this timeframe, Avaya Oceana® and the applications such as Avaya Breeze® platform nodes, System Manager, Avaya Control Manager, and Omnichannel Database remain powered on and accessible on the customer network but do not process any contacts or operations.

  • During the creation of snapshots, you must power down Avaya Oceana® and the applications such as Avaya Breeze® platform nodes, Avaya Control Manager, and Omnichannel Database.

• *** You must delete snapshots from Avaya Oceana® virtual machines before placing Avaya Oceana® back into production. Snapshots must only be taken or deleted when the virtual machine is powered down.