Cloning

No

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.

Storage DRS

No

Avaya Workspaces for Call Center Elite does not support this feature. There are impacts to the datastores. The input or output load balancing occurring in the production can cause outages.

Distributed Power Management (DPM)

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.

Fault Tolerance

No

High Availability (HA)*

No

• Avaya Workspaces for Call Center Elite does not support impacts to the virtual machines occurring in the production.

Snapshots***

Partial

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

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

Storage Thin Provisioning

Partial

• Yes, for SAN storage.

• No, for local hard disk storage.

vMotion

No

Avaya Workspaces for Call Center Elite does not support any form of vMotion as it can impact virtual machines to halt processing.

Storage vMotion

No

Avaya Workspaces for Call Center Elite does not support any form of vMotion including Storage vMotion, as it can impact the virtual machines to halt the processing.

Suspend and Resume

No

Cold Migration****

Yes

• You can do a cold Migration only on a virtual machine in a powered-off state by using vMotion.

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

Reservations on vCPU and memory required to be enabled

Yes

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

• Physical hosts running Avaya Workspaces for Call Center Elite virtual machines can have other virtual machines running and co-residing with the Avaya Workspaces for Call Center Elite virtual machines.

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

Hyperthreading

No

• Avaya Workspaces for Call Center Elite requires reservations. Therefore, Hyperthreading does not add any additional value.

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

* Avaya Workspaces for Call Center Elite provides its own HA mechanism.

** Maintenance mode 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 Workspaces for Call Center Elite 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 does not process any contacts or operations. During the creation of snapshots, you must power down Avaya Workspaces for Call Center Elite and the applications such as Avaya Breeze® platform nodes, Avaya Control Manager, and Omnichannel Database.

*** You must delete snapshots from Avaya Workspaces for Call Center Elite virtual machines before placing Avaya Workspaces for Call Center Elite back into production. Snapshots must only be taken or deleted when the virtual machine is powered down.

**** Cold Migration can only be performed on a virtual machine in a powered-off state.