A single VMware cluster can be shared between Avaya Oceana® 3.8.x and Avaya Analytics™ 4.x.

• The cluster contains virtual machines for Avaya Oceana® 3.8.x and Avaya Analytics™ 4.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 Deploying Avaya Oceana®.

Yes

For more information, see Deploying Avaya Analytics.

Cloning

No

No

Alternate mechanisms using BOSH.

Distributed Resource Scheduler (DRS)

Yes

For the documented guidelines in conjunction with affinity rules, see Deploying Avaya Oceana®.

Yes

For the documented guidelines on HA and DRS rules for Avaya Analytics™ 4.1.x, see Deploying Avaya Analytics.

Storage DRS

No

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

No

Avaya Analytics™ 4.1.x does not support datastore clusters.

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

Alternate mechanism using BOSH.

High Availability (HA)*

No

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

• For more information on configuring VMware HA in an Avaya Oceana® and Avaya Analytics™ single cluster deployment, see Deploying Avaya Oceana®.

Yes

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

• For the documented guidelines on HA and DRS rules for Avaya Analytics™ 4.1.x, see Deploying Avaya Analytics.

Snapshots***

Partial

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

• Remove snapshots before putting back contact center into production mode.

Partial

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

  Cluster Control Manager (CCM) — Remove snapshots before putting back contact center into production mode.

• All other Avaya Analytics™ Servers BOSH and the three Avaya Analytics™ VMs do not support the use of snapshots.

Storage Thin Provisioning

Partial

• Yes, for SAN storage.

• No, for local hard disk storage.

Yes

• Yes, for SAN storage.

• No local storage is supported.

  Note:

  Applicable to Avaya Analytics™ on HA.

• For more information on specifics of thin provisioning, see Deploying Avaya Analytics.

vMotion

Supported in maintenance mode only. Not supported in production mode.

For more information, see Deploying Avaya Oceana®.

Supported in maintenance mode only. Not supported in production mode.

For more information, see Deploying Avaya Analytics.

Storage vMotion

No

Avaya Oceana®/Avaya Analytics™ does not support any form of vMotion, including Storage vMotion, as it might impact real-time application behavior and event processing on virtual machines.

No

Avaya Oceana®/Avaya Analytics™ does not support any form of vMotion, including Storage vMotion, as it might impact real-time application behavior and event processing on virtual machines.

Suspend and Resume

No

No

Cold Migration

Yes

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

• Avaya Oceana® uses static IPs. Therefore, the new ESXi host must access the original data network and datastore for the migrated virtual machines.

Yes

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

• Avaya Analytics™ uses static IPs. Therefore, you can migrate Avaya Analytics™ virtual machines to hosts in the same VMware with 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 the production, 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.1.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 value.

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

Yes

* Avaya Oceana® provides its HA mechanism.

** Maintenance mode specifies a scheduled out-of-production window where Avaya Oceana® and other applications do not process contacts, all agents are logged out, and queues are empty. This timeframe is dedicated to patching, upgrades, and configuration tasks. 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. However, they do not process any contacts or operations. While creating 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 be taken or deleted when the virtual machine is powered down.