Best practice recommendations

Last Updated : Feb 03, 2023 |

Use the following best practices to deploy the Avaya Aura® MS appliance in the VMware® virtualized environment:

  • Media server VMs deployed as a High Availability (HA) cluster should be deployed on separate, equally capable host servers.

  • All physical servers that can host a VM must have the same CPU, memory, and networking specifications.

  • Physical CPUs on the host must not be oversubscribed with respect to vCPU count across all VMs that share the host with Avaya Aura® MS. A physical CPU refers to a physical CPU core and not to a hyper-thread. For example, the total number of vCPUs across all VMs on an ESXi host that has 12 physical cores with 24 hyper-threads, must not exceed 12.

    Note:

    This recommendation prevents CPU oversubscription. Therefore, the CPU reservation of the media server VM effectively enforces the minimum CPU core speed of the underlying hardware. The VM fails to start if the underlying hardware does not meet the core speed requirements.

  • Do not modify the CPU or memory reservations that are set for Avaya Aura® MS OVA.

    Note:

    Reservations are not permitted for Avaya Solutions Platform 4200 series solutions (formerly known as CPOD/PodFx) deployment. It is mandatory to ensure the ESXi host is not oversubscribed (pCPU <= vCPU for all VMs deployed to that host).

  • For maximum system performance, ensure that the energy savings features are disabled or that the maximum performance settings are enabled in the server BIOS.

  • When deploying the OVA file, select Thick Provision Lazy Zeroed option for the VM virtual disks.

  • If the physical network interfaces on the ESXi host are 10 Gbps interfaces, then NetIOC and traffic shaping must be performed. NetIOC and traffic shaping must allocate 1 Gbps of network bandwidth for the Avaya Aura® MS VM.

  • Old media server backup files must be removed to maintain free space on the system.

  • You must not modify any operating system files. Avaya manages the operating system on appliances. Modifying system files can cause future system layer updates from Avaya to fail or result in loss of your changes