TC2431en-Ed03 Virtualization OXE Configuration Related To OXE Releases and ESXi Infrastructure Versions

Technical Bulletin OmniPCX Enterprise
TC2431 ed.03 Release : all
Virtualization : OXE configuration related to

OXE releases and ESXi infrastructure versions
This document gives all necessary configuration details in order to install the OmniPCX Enterprise in VMware
virtualization infra.
Revision History
Edition 1: June 25, 2018 creation of the document

Edition 02: December 28, 2018 replace PC Install use by S.O.T.
Update virtualization values
Edition 03: October 30, 2019 rectifications and update
Legal notice:
The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE. To view other trademarks used by
affiliated companies of ALE Holding, visit: www.al-enterprise.com/en/legal/trademarks-copyright. All other trademarks are the
property of their respective owners. The information presented is subject to change without notice. Neither ALE Holding nor any
of its affiliates assumes any responsibility for inaccuracies contained herein. © 2019 ALE International. All rights reserved.
www.al-enterprise.com
Table of Contents
1 Reference ............................................................................................................................................... 4
2 Using VMware for OXE ............................................................................................................................ 5
3 Host and hypervisor configuration ............................................................................................................ 6

3.1 Host and hypervisor configuration ...................................................................................................... 6
3.2 OS GUEST Operating Systems for R12.x releases implemented in these patches and upper ................... 6
3.3 VMware Tools ................................................................................................................................... 6
3.4 Global configuration .......................................................................................................................... 7
3.4.1 OXE-V, OST64 and OMS VM configuration .................................................................................... 7
3.4.2 EEGW VM configuration............................................................................................................... 7
3.5 OXE-V drivers ................................................................................................................................... 7
3.6 CPU usage (processor used) .............................................................................................................. 8
3.6.1 OXE-V CPU usage (processor used) ............................................................................................. 8
3.6.2 OMS CPU usage (processor used) ................................................................................................ 8
3.6.3 EEGW CPU usage (processor used) .............................................................................................. 8
3.6.4 OST64 CPU usage (processor used) ............................................................................................. 8
3.7 RAM to be reserved ........................................................................................................................... 9
3.7.1 OXE-V RAM (exact value of RAM has to be reserved) .................................................................... 9
3.7.2 OMS, OST64 RAM (exact value of RAM has to be reserved) .......................................................... 9
3.7.3 EEGW RAM (exact value of RAM has to be reserved)..................................................................... 9
3.8 Disk usage ........................................................................................................................................ 9
3.8.1 OXE-V disk usage ....................................................................................................................... 9
3.8.2 OMS, OST64 and EEGW disk usage ............................................................................................ 10
3.9 VM virtual resources configuration ................................................................................................... 10
4 Limits and VM resource usage in traffic .................................................................................................. 10

4.1 CS : For a typical BHCC per business user of 5 calls/hour .................................................................. 11
4.2 CCD : For a typical BHCC per agent of 10 calls/hours ........................................................................ 13
4.3 4645 for a typical BHCC per business user of 5 ................................................................................. 14
4.4 4645 for a typical BHCC per business user of 5 in traffic <Contd.> .................................................... 14
4.5 CCD : Single redundant OXE-V ......................................................................................................... 15
4.6 OMS VM resource usage in traffic..................................................................................................... 16
4.7 OST64 VM resource usage ............................................................................................................... 16
4.8 EEGW VM resource usage................................................................................................................ 17
5 ATTRIBUTS AND COMPATIBILITIES FOR OXE VM ................................................................................... 17
6 COMPATIBILITY TABLES ....................................................................................................................... 18
6.1 ESXI infra 5.5 ................................................................................................................................. 18
6.2 ESXI infra 6.0 ................................................................................................................................. 19
6.3 ESXI infra 6.5 ................................................................................................................................. 20
6.4 ESXI infra 6.7 ................................................................................................................................. 21
OmniPCX Enterprise - Release : all

Virtualization : Configuration of OXE following releases and ESXi infra version TC2431 ed.03
Copyright © ALE International 2019 page 2/70
7 EXAMPLE OF A CREATION OF R12.2 RELEASE ........................................................................................ 21
7.1 Installation of the OmniPCX Enterprise VM through The OmniPCX Enterprise Installer. ...................... 22
7.2 vSphere web client creation after the choice of the OS guest ............................................................. 47
8 Use of S.O.T. to install omniPCX version on the virtual machine. .............................................................. 54
9 BEHAVIOR AROUND VIRTUALIZATION ................................................................................................... 56
10 APPENDIX ........................................................................................................................................... 58
10.1 Multi-instance general rules ........................................................................................................... 58

10.2 The GHz rule................................................................................................................................. 58
10.3 The maximum CPU over provisioning ratio rule ............................................................................... 58
10.4 Multi-instance examples ................................................................................................................ 59
10.5 OMS port dimensioning ................................................................................................................. 60
10.6 Workaround for creation of OVA/OVF with VMWare applications ...................................................... 62
10.6.1 OVA/OVF with VMWare applications ......................................................................................... 62
10.6.2 New tool within WMware Workstation ...................................................................................... 62
10.6.3 VMWare applications : ovf-tool ................................................................................................ 65
10.6.4 VMWare applications : VMware converter ................................................................................. 66
10.7 VM attributs details ....................................................................................................................... 66

1 Reference
OpenTouch Suite for MLE virtualization design guide TBE043
OpenTouch Suite for MLE in virtualized environment, overview [TBE031]
Official documentation package for OXE
Ex : OXE R12.3.1 Documentation package (All languages)
TC2456 Software Orchestration Tool (S.O.T.) Release Note of version R2.2 (2.2.003.008)

2 Using VMware for OXE
VMware is a complex OS which can supported most of guest OS.

Configuration of HOST and virtual machine is really important.
The server on which the VMware OS (Hypervisor, VMware workstation) is really important too.
License of the hypervisor is the attribute which can give more and more possibilities if you have the
high license for your ESXi infra.
For the OmniPCX Enterprise(OXE) there is lot of different configurations for creation of virtual
machine.
It depends of ESXI infra and the release of OXE.
Between R11 and lower versions, and R12 and upper versions, the possibilities are completely different.
This is true for OXE, OMS OST64 EEGW and 4645 because all depend of the OXE system.
Please consider the document TBE043 - OT Suite for MLE - Virtualization Design Guide - Edxxd - H2
2019 offer to have complete global informations around virtualization, countings and resources
requires, ALE rules, and supported practices.

3 Host and hypervisor configuration
3.1 Host and hypervisor configuration

• Hypervisor VMware ESXi 6.7, 6.5, 6.0, 5.5 are supported
• Power management options have to be disabled, or configured for maximum
performances at BIOS and hypervisor level
• Hyperthreading can be enabled at BIOS and hypervisor level
• No minimum core frequency, it depends only on VM CPU needs
3.2 OS GUEST Operating Systems for R12.x releases implemented in these

patches and upper
OS GUEST Centos 6 32 bits can be used for R12.X release. To not have a warning from
VMWare, the newer base system and centos-release packages will be integrated in the
following releases and upper.
m4 implemented
m3.402.24.a
m3.402.25 (MD3)
m2.300.24
m2.300.25 (MD8)
m1.403.26 (MD11)
A Hotfix exists for all R12.x release and patch.
• Guest operating system

• OXE-VM – CENTOS-4/5/6 32-bit
• OMS, OST64 and EEGW – SUSE LINUX ENTERPRISE 12 64-bit
3.3 VMware Tools

It is mandatory to install VMware tools in OXE-V VM since OXE R12.x with Linux kernel
version 2.6 32 bits or Centos 4/5/6 32 bits (see TC 2432 VMTOOLS on OXE - How To)
• VMware tools have to be installed in OMS, OST64 and EEGM VMs
VMWare tools is not enabled for release R11 and lower

3.4 Global configuration
3.4.1 OXE-V, OST64 and OMS VM configuration
• 1 vCPU.
• “Hyper-threading sharing core” parameter of the VMs has to be configured as “none”
for ESXi <= 6.0.
• “VMware CPU Scheduling affinity” cannot be used
• RAM in MB depends on provisioning level and have to be reserved according to the
OXE-V/OMS/OST64 VM resource usage indicated in “VM resource usage in traffic”
slides.
• Thin provisioning of virtual hard disk can be used.
• Disk attribute : Independent persistent are recommended.
• SCSI controller: LSI Logic parallel with a disk virtual device node SCSI(0:0)
recommended due to higher performance
• Network adapter: vmxnet3 R12.x with OS Guest Centos 4/5/6 32 bits, otherwise
E1000 is used.
3.4.2 EEGW VM configuration

• Number of vCPUs: 1 vCPU <= 7K users >= 2 vCPUs => 15K users
• “Hyper-threading sharing core” parameter of the VMs has to be configured as
“none” for ESXi <= 6.0.
• “VMware CPU Scheduling affinity” cannot be used
• RAM in MB depends on provisioning level and have to be reserved according to
the EEGW VM resource usage indicated in “VM resource usage in traffic” slides.
• Thin provisioning of virtual hard disk can be used.
• Disk attribute: Independent persistent are recommended.
• SCSI controller: LSI Logic parallel with a disk virtual device node SCSI(0:0)
• Network adapter: vmxnet3
3.5 OXE-V drivers

See chapters 6 for details relative to releases.

3.6 CPU usage (processor used)
3.6.1 OXE-V CPU usage (processor used)
The minimum CPU reservation is fixed to 200 MHz, whatever the result of the
following rules
• 10 MHz per 1000 standard business calls/hour (BHCC) (1/3rd local calls, 1/3rd
outgoing external calls, 1/3rd incoming external calls)
• 12 MHz per 1000 call center calls/hour (BHCC) w/o IVR scenario (either
incoming or outgoing calls) (+15% Vs business calls)
• 20 MHz per 1000 call center calls/hour w/ IVR (SIP or TDM) scenario (either
incoming or outgoing calls) (+100% Vs business calls)
• 80 MHz for 8 4645 ports, 100 MHz for 16 4645 ports, 150 MHz for 30 4645
ports
• Other specific usages may use different CPU loads and will have to be benchmarked
on site
3.6.2 OMS CPU usage (processor used)

• 100 MHz for OS internal needs
• 5 MHz per G711 leg
• Unless a deep analysis has been performed, if G729 codec is required, all legs have
to be considered as G729 legs
3.6.3 EEGW CPU usage (processor used)

• 150 MHz per 1000 Encrypted IP calls/hour (BHCC) – For <7K Users
• 170 MHz per 1000 Encrypted IP calls/hour (BHCC) – For >7K Users
3.6.4 OST64 CPU usage (processor used)

• 420 MHz per 1K Users ( up to 5K users)

3.7 RAM to be reserved
3.7.1 OXE-V RAM (exact value of RAM has to be reserved)
• OXE-V RAM usage (exact value of RAM has to be reserved):
• 1024 for releases < R12 release
• 1024 MB for less than 7K users
• 2048 MB for more than 10K users
3.7.2 OMS, OST64 RAM (exact value of RAM has to be reserved)

• 1024 MB
3.7.3 EEGW RAM (exact value of RAM has to be reserved)

• 1 GB for 1.5K encrypted users
• 2 GB for 7K encrypted users
• 3 GB for 15K encrypted users
3.8 Disk usage
During startup phase, disk usage is far more important than during traffic.
Typical disk bandwidth average values: 300KB/s in read, 25KB/s in write.
Typical disk bandwidth peak values: 1500KB/s in read, 100KB/s in write.
CPU usage may rise up to 500MHz but doesn’t have to be reserved.
3.8.1 OXE-V disk usage

The OmniPCX Enterprise VM supports RAID - Redundant Array of Independent Disks -,
however UPS is not supported.
As of R10.1.1, an OmniPCX Enterprise hosted on a virtual machine, can rely on a SAN
(Storage Area Network) rather than a virtual disk.
The SAN allows the VMotion feature: a virtual machine, hosting an OmniPCX Enterprise, can
be moved from a physical ESXi server to another, without interruption of service.
The VMotion feature is available:
• For the main OmniPCX Enterprise with very light traffic
• For the standby OmniPCX Enterprise

• 40 GB if users number <= 1500 and mailboxes number <= 1000 and 4645
ports <= 8
• 60 GB if users number > 1500 or mailboxes number > 1000 or 4645 ports
>8
• 80 GB if mailboxes number > 3000
• 80 GB if more than 600 hours of stored voice messages are required or
more than 3K mailboxes
3.8.2 OMS, OST64 and EEGW disk usage

• 4 GB
3.9 VM virtual resources configuration

• Disk bandwidth and IOPS: see tables in upcoming chapters
• Network bandwidth and IOPS: depends on topology, connected sets…
4 Limits and VM resource usage in traffic

Most of limits values are done for R12. But these limits or counts are true for other releases.
• The sum of all CPU reserved by VMs cannot exceed 90% of the available CPU on the
host (10% are reserved for ESXi usage)
• 8 OXE-V OST64 EEGW VM maximum per physical core (max CPU over provisioning =
8)
• 4 OMS VM maximum per physical core (max CPU over provisioning = 4)
• See Appendix on GHz and CPU over provisioning rules
• VMs should be configured with the needed features that accounts for a margin of
about 20% to avoid the VM overload condition (exclusive of 10% are reserved in
ESXi usage)
• All limits and provisioning level of non virtualized OXE are applicable

4.1 CS : For a typical BHCC per business user of 5 calls/hour
Example the typical CPU is:
(*) Half of the ports reading voice messages, other half recording messages
=> see this table next slide – for various table the number of required vCPUs

(**) Other specific usages may use different CPU loads and will have to be benchmarked on
site
(***) In case of a co-hosted A4645 voicemail and more than 600 hours of stored voice
messages are required, 80 GB of virtual hard disk will be necessary.
(***) In case only 3000 mailboxes are present on the embedded A4645, 60 GB of virtual
hard disk are enough.

4.2 CCD : For a typical BHCC per agent of 10 calls/hours
Example: the typical CPU usage is:
Typical disk bandwidth peak values: 1500KB/s in read, 100KB/s in read.

4.3 4645 for a typical BHCC per business user of 5
Example: the typical CPU usage is:
 see table in next slide

(*) Half of the ports reading voice messages, other half recording messages.
Typical disk bandwidth peak values: 1500KB/s in read, 100KB/s in read.
4.4 4645 for a typical BHCC per business user of 5 in traffic <Contd.>

4.5 CCD : Single redundant OXE-V
Single redundant OXE-V with 1450 business users, 320 agent users without IVR
integration and voicemail for all business users (30 ports)
(*) voicemail disk usage is not taken into account

(**) Half of the ports reading voice messages, other half recording messages

4.6 OMS VM resource usage in traffic
See Appendix : port dimensioning to determine the codecs, number of ports and MHz
needed depending on OMS features and usages
(*) Unless a deep analysis has been performed, if G729 codec is required, all ports have
to be considered as G729 ports.
4.7 OST64 VM resource usage
No of Users : (REG Only) 2000 5000 5000-7000
CPU usage in MHz 840 2100 NA

Required vCPU 1 1 1
RAM usage in MB 1024 1024 1024
Disk usage in GB 4 4 4

4.8 EEGW VM resource usage
Users number: 1000 2000 7000 8000 10000 15000
CPU usage in MHz 150 300 1050 1360 1700 NA

Required vCPU 1 1 1 2 2 2
RAM usage in MB 1024 1024 1024 2048 3072 3072
Disk usage in GB 4 4 4 4 4 4
5 ATTRIBUTS AND COMPATIBILITIES FOR OXE VM

The installation of more than one virtual machine hosting an OmniPCX Enterprise on the same
physical server requires a compatible VMware hardware version :
https://kb.vmware.com/s/article/1003746

6 COMPATIBILITY TABLES
6.1 ESXI infra 5.5

OXE R11 and < OXE R12.0 OXE R12.1 OXER12.2 and
upper
HARDWARE 7 to 8 7 to 10 7 to 10 7 to 10
VERSION
OS GUEST Other linux 32 bit Other 2.6 32 bit Other 2.6 32 bit Other 2.6 32 bit
DISK TYPE IDE SCSI SCSI SCSI
DISK SIZE See 3 chapter See 3 chapter See 3 chapter See 3 chapter
DISK ATTRIBUT Independent - Independent - Independent - Independent -

recommended persistent persistent persistent persistent
NIC E1000 E1000 E1000 E1000
MEMORY See 3 chapter See 3 chapter See 3 chapter See 3 chapter
MEMORY YES mandatory YES mandatory YES mandatory YES mandatory

RESERVED
CPU See Appendix See Appendix See Appendix See Appendix
INFRA VMWARE NO YES YES YES

TOOLS

6.2 ESXI infra 6.0
upper
HARDWARE 7 to 11 11 11 11
VERSION
OS GUEST Other linux 32 bit Centos 4/5/6 32 bit Centos 4/5/6 32 bit Centos 4/5/6 32 bit

NIC E1000/Flexible VMNETX3 VMNETX3 VMNETX3
MEMORY See 3 chapter See 3 chapter See 3 chapter See 3 chapter

RESERVED

TOOLS

6.3 ESXI infra 6.5
VSphere Web client mandatory
upper
VERSION
OS GUEST Other linux 32 bit Centos 6 32 bit Centos 6 32 bit Centos 6 32 bit

MEMORY See 3.1 chapter See 3.1 chapter See 3.1 chapter See 3.1 chapter

RESERVED

TOOLS

6.4 ESXI infra 6.7
VSphere Web client mandatory
upper
VERSION
OS GUEST Other linux 32 bit Centos 6 32 bit Centos 6 32 bit Centos 6 32 bit

MEMORY See 3.1 chapter See 3.1 chapter See 3.1 chapter See 3.1 chapter

RESERVED

TOOLS
7 EXAMPLE OF A CREATION OF R12.2 RELEASE
This example has to be adapted to the compatibility table from the precedent chapter.
Prerequisites
To guarantee system BHCC for 15000 pieces of equipment, these requirements are:
• Dedicated and reserved memory:
o 1 GB of RAM recommended for ESXi 5.5 with OS other linux 2.6 32 bits
o See table 4.1 for recommended of RAM for ESXi 6.0 with OS Centos 4/5/6 32 bits

o See table 4.1 for recommended of RAM for ESXi 6.5, 6.7 with OS Centos 6 32
bits
• Virtual hard disk:
o Minimum of 40 GB with small voice mail storage capacity.
o Maximum of 80 GB in case of more than 600 hours voice mail storage
• Disk bandwidth and IOPS: refer to:
o https://businessportal2.alcatel-lucent.com/ENT_MLE_015903
• 1 or 2 vNIC (redundancy dependent)
• Processing: one vCPU. There is no minimum core frequency. (see count above)
• Frequency used: MHZ = max (200, 12 * traffic in Ko calls per hour) for standard business
traffic (5 BHCC per user with one third of local calls, two third of incoming/outgoing calls)
• SCSI controller: LSI Logic parallel with a disk Virtual Device Node set to ScSI(0:0)
• Network adapter: VMXNET3 for Centos OS guest and E1000 for other OS guest
7.1 Installation of the OmniPCX Enterprise VM through The OmniPCX

Enterprise Installer.
All details done below are true for vSphere or vCenter client. There are some difference
following the Vmware infra in menus but choices are the same.
Step 1 : All double click the VMware vSphere icon to start the vSphere client
You can also start the vSphere management console via Start Menu -> All Programs
-> VMware -
> vSphere or vCenter Client for ESXI 5.5 and 6.0

Step 2 : Open the vSphere client and login with your user credentials
• IP address: <Your VMware ESXi hypervisor server>
• Username: root
• Password: <Assigned at installation>
Note:
This password has been defined during the VMware ESXi installation on the server.
Click Login

In some cases, a security warning is displayed
If you receive a Certificate Warning, select Install this certificate and do not display any
security warnings for "172.19.32.220", and click Ignore.
Note:
Certificate Warnings are generated automatically, unless you are working within an internal
PKI infrastructure.

Step 3 : Connect to VMWare vSphere from your browser to start vSphere client
From ESXi 6.5 it is mandatory to use the vSphere Web Client (Flash) via an URL ex :
https://10.15.8.100 : ESXi or vCenter IP address
Step 4 : Open the vSphere client and login with your user credentials
•Username: <Your login> or root
• Password: <Assigned at your login> or root password
Note:
This password has been defined during the VMware ESXi installation on the server.

Step 5 : When you click on server or cluster the VMware vSPHERE shows you
the inventory
VSphere client inventory page example
VSphere Web client inventory page example
Right click the IP address of the ESXi hypervisor to open the contextual menu and select
New Virtual Machine.

Step 6 : Right click the IP address of the ESXi hypervisor to open contextual menu and
select NEW VIRTUAL MACHINE
VSphere client inventory page example
vSphere Web client New virtual machine creation example

Step 7 : Select the Custom button and click next
VSphere client configuration page example
vSphere Web client new popup : choose Next

Step 8 : Enter a name for the virtual machine and click next
Note:
For best practice, give the same name to the virtual machine and the OmniPCX Enterprise.

Step 9 : vSphere client configuration is a little bit different
We will see after a complete creation via vSphere web client
In the same popup you give :

o Name of the virtual machine
o The hardware version on which the machine will turn
o The OS guest type : linux
o The OS diversity : Centos 6 32 bits (depend of OXE release and infra)

Step 10 : Select the datastore used by the virtual machine and click next

Step 11 : Select the Virtual machine hardware version compliant with your VMWare ESXi
infra and click next

Step 12 : Select Linux as Guest Operating System and Centos 6 (32 bits) as
Guest OS. Click next

Step 13 : Select Number of virtual sockets and Number of cores per virtual socket to
define the performance of the CPU of your virtual machine (see counts above and in
Appendix)

Step 14 : Select the memory size used by your virtual machine according to virtual
machine requirements and click next

Step 15 : Select the Network adapter and click next
If the Linux OS version is CentOS 4/5/6 (32-bit), or Centos 6 (32 bit) select VMXNET 3
If the Linux OS version is Other Linux 2.6 (32-bit) or other Linux (32 bits) , select E1000

Step 16 : Select the LSI logical Parallel option and click next
Centos guest do not supported the VMware paravirtual.

Step 17 : Select the create a new virtual disk option and click next

Step 18 : Select a disk size and click next
Thin provisioning is supported.

Step 19 : Select ScSI(0:0) as virtual device Node and click next
Depend of your ESXi Infra and OXE release.
Recommended : click on Independent- persistent : these attributs give the I/O more native
to the disk access.
Attention : Independent- persistent disabled snapshots : so depend of your datacenter
backups
The Ready to complete page is displayed

Step 20 : Verify the settings defined for your virtual machine and go to edit settings
This is to reserve all the memory. Memory must be dedicated to the OXE.

Step 21 : Click on the tab resources

Step 22 : Reserved the memory and give the unlimited value to the CPU
• Reserved the memory and check CPU values

• Click Back to modify parameters
• Click Finish to create the virtual machine

7.2 vSphere web client creation after the choice of the OS guest
You have in the popup all parameters to configure. But finally the result is the same

Step 1 : Select Number of virtual sockets and Number of cores per virtual socket to define
the performance of the CPU of your virtual machine
• Open CPU target : unlimited means reserved

Step 2 : Select the memory size used by your virtual machine according to the virtual
machine requirements
• Open the Memory target
• Reserved the memory

Step 3 : Select the Network adapter
• If the Linux OS version is CentOS 4/5/6 (32-bit), Centos 6 (32 bit) select VMXNET 3
• If the Linux OS version is Other Linux 2.6 (32-bit), or other Linux (32 bit) select
E1000
• Open the NIC adapter

Step 4 : Select the LSI Logic Parallel option
• Open ScSI controller target

Step 5 : Manage the virtual disk with all options in the same view
• Open the Hard disk 1 target
• And give the following configuration :
- Size of the disk : see chapter 3.1
- ScSI controller
- Independent – persistent : recommended
Attention : Independent- persistent disabled snapshots : so depend of your datacenter
backups
The Ready to complete page is displayed

Step 6 : Verify the settings defined for your virtual machine
• Click Back to modify parameters

• Click Finish to create the virtual machine

8 Use of S.O.T. to install omniPCX version on the virtual machine.
See also technical documentation and release note about S.O.T.
Notice that the “K2” type used for any country is not proposed for the moment in that tool
Below, some screen shots related to this kind of installation (taken from an installation using
a workstation. OXE vm is installed locally on a PC. Can be applied also in an ESXi
environment).

The patch has to be chosen from the iso file declared as an internal PC media.
Note: that the Thales version of secured version cannot be installed directly. You need to
install the last patch (dynamic or static) and always finish by that secured patch.
9 BEHAVIOR AROUND VIRTUALIZATION

 Snapshot , if needed, must be done virtual machine stopped. Have only one snapshot
stored (ALE rule) otherwise you can slow down the I/O. VMWare snapshosts are not
backups : it only takes a copy of the changes (disk delta)
 Clone , if needed, must be done virtual machine stopped
 VMware let you modify the type of the disk : but don’t do this because the OS of OXE
create partitions and registered the driver used for the disk. If you change the type
(ex IDE  SCSI) the OS do not start.
 Hyperthreading : yes for virtual machine OXE since ESXi 6.0.
 Reminder : for release R11 and lower, disk must be IDE; from R12 and upper, disk
be ScSI

 Disk independent-persistent recommended : means Independent disks are
unaffected by snapshots, persistent changes are written immediately and
permanently to disk

10 APPENDIX
10.1 Multi-instance general rules

 To run flawlessly, a virtual machine needs to have sufficient physical resources. If it
is easy to understand with RAM and disk (there is only one factor, the quantity) it’s
more complex when dealing with CPU.
 In this case, two factors have to be considered for the VM needs:
o The number of virtual CPU (vCPU) of the VM.
o The number of GHz the VM needs
• Similarly, the physical host provides:

o A given number of cores
o A given number of GHz, the core frequency * the number of physical cores.
10.2 The GHz rule
• When running several OXE-V and or OMS virtual machines on the same
physical host, two rules have to be simultaneously enforced :
- The first one is the GHz rule:
The sum of all the VM needs in GHz running on the same physical host has to
be less (or equal) than 90% of the total GHz available in this host (10% are
dedicated to ESXi usage).
10.3 The maximum CPU over provisioning ratio rule

- The second one is the maximum CPU over provisioning ratio rule:
This ratio is the total number of vCPU declared in all the VM running on the
physical host divided by the physical cores number available in the host.
The maximum ratio is 8 for OXE-V & OST64, 4 for OMS.
When several VM with different ratio run on the same physical host, the
smallest ratio has to be used.

10.4 Multi-instance examples
• How many cores at 2.4 GHz are needed to run 2 OXE with 100 users each
(200MHz usage per VM) and 2 OMS with 20 G711 channels (200 MHz usage
per VM)?
The GHz rule give 4*0.2Ghz/0.9 =0.9 Ghz. So the final requirement is 1 core@2.4
Ghz.
The OMS max CPU over provisioning rule for 4 vCPU gives 1 core
=> 1 cores at 2.4GHz.
• How many cores at 2.4 GHz are needed to run 3 OXE with 15K users each
(900MHz usage per VM)?
The GHz rule give 3*0.9GHz/0.9 = 3GHz (2 cores@2.4GHz or 1 core@3GHz).
The OXE max CPU over provisioning rule for 4 vCPU gives 1 core
=> 2 cores at 2.4GHz (or 1 core at 3GHz).
(200MHz usage per VM)?
The GHz rule give 10*0.2GHz/0.9 = 2.2GHz (1 core@2.4 GHz).
The OXE max CPU over provisioning rule for 10 vCPU gives 2 cores
=>2 cores at 2.4 GHz.

(200MHz usage per VM) and 5 OMS with 20 G711 channels (200 MHz usage
per VM)?
The GHz rule give 10*0.2GHz/0.9 = 2.2 GHz (1 core).
The max CPU over provisioning rule to use is the OMS one. It gives 3 cores
for 10 vCPU.
(200MHz usage per VM), 5 OMS with 20 G711 channels (200 MHz usage per
VM) and a 3rd party VM with 4 vCPU and without GHz reservation?
The GHz rule give 10*0.2GHz/0.9 = 2.2 GHz (1 core).
The max CPU over provisioning rule to use is the OMS one. It gives 4 cores
for 14 vCPU.
Note:

GHZ rule: The sum of all the VM needs in GHz running on the same physical host has to be
less (or equal) than 90% of the total GHz available in this host (10% are dedicated to ESXi
usage).
10.5 OMS port dimensioning

The blocking rate used in OMS contexts is 0.1%.
Voice guides
Applies to OXE users only, for each zone where OXE-MS is deployed. The number of users
to be considered follows the principles stated in the previous section.
Pv = E2P (voice guides erlangs per user * number of OXE users)
MoH
Pm = E2P (MoH erlangs per user * number of OXE users)
3-way conferencing
P3 is computed the same way as in OpenTouch, where the computed number of ports P is
adjusted to compensate for small populations:
P = E2P (3-way conf erlangs per user * number of OXE users)
Number of conferences = (P + 8) / 3, rounded to the lowest integer
P3 = number of conferences x 3
Equals zero if there is no need for the feature.
Pre-offhook and DISA
Apply to OXE users only, in Central Zone only.
Usage of pre-offhook and DISA is subject to options.
The number of erlangs is expressed per public SIP trunk access, as input in the FI “SIP
Network Links”.
The number of SIP Network Links is supposed to be sized to handle the external traffic of
both OXE and OT Conversation populations, whereas pre-offhook and DISA usages only
apply to the OXE population. For this reason, the corresponding number of SIP Network
Links required for public SIP access of the OXE population is first computed using the
reverse erlang function P2E() introduced in section 5.

Trunks = E2P(P2E(SIP Network Links) * OXE users / (OXE users + OT Conversation
users))
Po = E2P(Trunks * (Pre-offhook erlangs per trunk + DISA erlangs per trunk))
The number of SIP Network Links is also supposed to handle the additional traffic
induced by OXE users accessing OT services, such as voicemail and conferencing, and
which should also be excluded from what applies to the usages considered here.
Ringback
Required when some SIP providers require to provide a ringback on all external inbound
calls.
Applies to both OXE and OT Conversation users, in Central Zone only.
The number of erlangs is expressed per user, applied to every inbound call for 1/3rd of total
calls in enterprise contexts, and assuming an average ringing time of 7s.
Ringback Erlangs = 5/3 * 7s / 3600 = 0.0032 E / user
Pr = E2P (0.0032 * number of OXE + OT Conversation users)
Equals zero if there is no need for the feature.
This computation is independent of the number of public SIP trunk accesses, but can
also be expressed per SIP Trunk access.
Transcoding
Transcoding essentially addresses cases where a SIP service provider would restrict external
traffic to G.711 only, while the deployment would impose G.729 internally in some areas.
Computation requires to know the number of such areas, from which a proportion Pcomp
of G.729-only users is computed.
Transcoding applies to both OXE and OT Conversation users, when the following conditions
are met:
• The SIP provider restricts to G.711 only
• Pcomp > 0
To compute the number of simultaneous calls to be transcoded, an erlang of 0.16 * 2 / 3 =
0.107 is assumed. The figure will need to be adjusted if an assumption different than 0.16 E
is made.
calls = E2P(0.107 * (number of OXE + OT Conversation users) * Pcomp)
Pt = calls * 2
Additionnal resources
The last pool of resources Pa is not computed but freely input using a dedicated FI named
“Number of additional accesses”.

10.6 Workaround for creation of OVA/OVF with VMWare applications
It is possible to use different VMWare tools for :
 Creation of OXE
 Creation of OVF/OVA
 Deployment of these OVA/OVF in a datacenter or ESXi for a customer
SOT is the tool you need to focus.
10.6.1 OVA/OVF with VMWare applications
Consider that your VMWare Workstation has specific drivers and VMware hardware
version.
You need to prepare the OVA/OVF to be available for most of ESXi VMWare hardware
version.
After you can updating the compatibility of the hardware version after deployment.
https://kb.vmware.com/s/article/1003746
It will just take care to estimate the size and drive type (SCSI and the LSI controller
parallel) discs since these are the only non-editable items for a VM already built. Do not
put a hardware build version upper than the infrastructure of the customer : you can
put underneath the leaves to adjust at deployment.
Do not install the VMware workstation tools in the OXE.
At the time of deployment of OVF:

 uncheck the automatic start
 Adjust the guest OS based client infrastructure moving closer to more just the
guest system.
 Check disks
 Reserve memory for OXE and OMS (OVA/OVF does not carry this attribute)
 Check the type of Ethernet card (vm3xnet) for OXE and adjust its VLAN
 Start installing VMware tools VMs that need.
10.6.2 New tool within WMware Workstation

New tools in Workstation : it is possible to connect to an ESXi directly in adding the
IP address of the ESXi. Then you can upload directly a created OXE VM on VMWare
server.

 Select the OXE VM to upload on the ESXi and
 Upload to the connected ESXi

10.6.3 VMWare applications : ovf-tool
Create an OVA/OVF can be done with the :
 ovf-tool : VMware-ovftool-4.3.0-13981069-win.i386.msi (ex)
https://my.vmware.com/fr/group/vmware/details?productId=614&downloadGroup=
OVFTOOL420
https://www.vmware.com/support/developer/ovf/ovf350/ovftool-350-userguide.pdf
https://docs.ukcloud.com/articles/vmware/vmw-how-use-ovf-tool.html
Example of use
C:\Program Files\VMware\VMware OVF Tool>ovftool d:\vmOXE\vmOXEt.vmx

d:\vmOXE.ova
Opening VMX source: d:\vmOXE\vmOXEt.vmx
Opening OVA target: d:\vmOXE.ova

Writing OVA package: d:\vmOXE.ova
Transfer Completed
Completed successfully
25/10/2019 08:53 446 898 176 vmOXE.ova
10.6.4 VMWare applications : VMware converter

VMWare converter : VMware-converter-en-6.1.1-3533064.exe (ex)
https://my.vmware.com/fr/web/vmware/info/slug/infrastructure_operations_manage
ment/vmware_vcenter_converter_standalone/6_2_0
VMware Converter automates and simplifies the conversion of physical machines into
virtual machines, as well as conversions between virtual machine formats. Driven by
a wizard, the intuitive interface of VMware Converter allows you to convert your
physical machines into virtual machines.
http://www.vmwarearena.com/vmware-converter-how-to-perform-p2v-and-v2v-
migration/
10.7 VM attributs details
To obtain the content of a vmx file follow this link :

http://sanbarrow.com/vmx.html
Detailed Description
Creates a new virtual machine with the provided parameters. The network adapter and the
SCSI adapter of the new virtual machine are created of the recommended type for the OS
that is specified by the GuestId parameter. If the OSCustomizationSpec parameter is used,
the virtual machine is customized according to the spec.
Parameters
Name Description Requir Pipeli Defa

ed? ne ult
Input Valu
e
true
Specify the host on which you want to create the new virtual
VMHost true (ByVal
machine.
ue)
Specify the version of the new virtual machine. The valid values
Version are v4 and v7. By default, the new virtual machine is created false false
with the highest available version.
Specify a name for the new virtual machine. If you are
Name registering or cloning an existing virtual machine, this parameter true false
is not mandatory.
Specify the resource pool where you want to place the new true
ResourcePool virtual machine. If not specified, the virtual machine is added to false (ByVal
the resource pool of its host. ue)
true
Specify the virtual appliance where you want to create the new
VApp false (ByVal
virtual machine.
ue)
Specify the folder where you want to place the new virtual
Location false false
machine.
Specify the datastore where you want to place the new virtual
Datastore false false
machine.
Specify the size in MB of the disks that you want to create and
DiskMB false false 4096
add to the new virtual machine.
Specify paths to virtual disks you want to add to the new virtual
DiskPath false false
machine.
DiskStorageFo Specify the storage format of the disks of the virtual machine.
false false
rmat The valid values are Thin and Thick.
MemoryMB Specify the memory size in MB of the new virtual machine. false false 256
Specify the number of the virtual CPUs of the new virtual
NumCpu false false 1
machine.
Indicate that you want to add a floppy drive to the new virtual
Floppy false false
machine.
Indicate that you want to add a CD drive to the new virtual
CD false false
machine.
Specify the guest operating system of the new virtual machine.
See below the valid values for the various ESX versions.
GuestId false false
Depending on the hardware configuration of the host, some of
the guest operating systems might be inapplicable.

For ESX servers older than ESX 4.0, the following values are
valid:
https://www.vmware.com/resources/compatibility/pdf/VMwar
e_GOS_Compatibility_Guide.pdf
Specify the full OS name of the new virtual machine. Use this
AlternateGues
parameter if the GuestID parameter is set to otherGuest or false false
tName
otherGuest64.
NetworkNam Specify the networks to which you want to connect the new
false false
e virtual machine.
Specify the HA restart priority of the new virtual machine. The
valid values are Disabled, Low, Medium, High, and
ClusterRestartPriority. VMware HA is a feature that detects
HARestartPrio failed virtual machines and automatically restarts them on
false false
rity alternative ESX hosts. Passing values to this parameter through a
pipeline is deprecated and will be disabled in a future release.
Specifying this parameter is only supported when the virtual
machine is inside a cluster. Otherwise, an error is generated.
Indicates whether the virtual machine should be powered off if a
host determines that it is isolated from the rest of the compute
resource. The available values are AsSpecifiedByCluster,
HAIsolationRe PowerOff, and DoNothing. Passing values to this parameter
false false
sponse through a pipeline is deprecated and will be disabled in a future
release. Specifying this parameter is only supported when the
virtual machine is inside a cluster. Otherwise, an error is
generated.
Specify a DRS (Distributed Resource Scheduler) automation
level. The valid values are valiFullyAutomated, Manual,
DrsAutomatio PartiallyAutomated. Passing values to this parameter through a
false false
nLevel pipeline is deprecated and will be disabled in a future release.
Specifying this parameter is only supported when the virtual
machine is inside a cluster. Otherwise, an error is generated.
Specify the swapfile placement policy. The following values are
valid:
VMSwapfileP InHostDataStore - Store the swapfile in the datastore specified

false false
olicy by the VMSwapfileDatastoreID property of the virtual machine
host. If the VMSwapfileDatastoreID property is not set or
indicates a datastore with insufficient free space, the swapfile is
stored in the same directory as the virtual machine. This setting

might degrade the VMotion performance.
With VM - Store the swapfile in the same directory as the virtual

machine.
This parameter is supported only on vCenter 2.5, ESX 3.5, and

later..
Specify the vSphere servers on which you want to run the
cmdlet. If no value is given to this parameter, the command runs
Server false false
on the default servers. For more information about default
servers, see the description of Connect-VIServer.
Indicate that the command returns immediately without waiting
for the task to complete. In this mode, the output of the cmdlet
RunAsync is a Task object. For more information about the -RunAsync false false
parameter run " help About_RunAsync" in the vSphere PowerCLI
console.
Provide a description of the new virtual machine. The alias of
Description false false
this parameter is Notes.
Indicate that the cmdlet is run only to display the changes that
WhatIf false false
would be made and actually no objects are modified.
If the value is $true, indicates that the cmdlet asks for
$tru
Confirm confirmation before running. If the value is $false, the cmdlet false false
e
runs without asking for user confirmation.
Specify the virtual machine template you want to use for the
true
creation of the new virtual machine. Passing values to this
Template true (ByVal
parameter through a pipeline is deprecated and will be disabled
ue)
in a future release.
OSCustomizati Specifies a customization specification that is to be applied to
false false
onSpec the new virtual machine.
VMFilePath Specify a path to the virtual machine you want to register. true false
true
VM Specify a virtual machine to clone. false (ByVal
ue)

Submitting a Service Request
Please connect to our eService Request application.
Before submitting a Service Request, please be sure:

 The application has been certified via the AAPP if a third party application is involved.
 You have read the release notes that list new features, system requirements, restrictions, and more,
and are available in the Technical Documentation Library.
 You have read through the related troubleshooting guides and technical bulletins available in the
Technical Documentation Library.
 You have read through the self-service information on commonly asked support questions and known
issues and workarounds available in the Technical Knowledge Center.
- END OF DOCUMENT -


TC2431en-Ed03 Virtualization OXE Configuration Related To OXE Releases and ESXi Infrastructure Versions

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

TC2431en-Ed03 Virtualization OXE Configuration Related To OXE Releases and ESXi Infrastructure Versions

Uploaded by

Copyright:

Available Formats

Technical Bulletin OmniPCX Enterprise

TC2431 ed.03 Release : all

Virtualization : OXE configuration related to

Edition 1: June 25, 2018 creation of the document

3 Host and hypervisor configuration ............................................................................................................ 6

4 Limits and VM resource usage in traffic .................................................................................................. 10

OmniPCX Enterprise - Release : all

10.1 Multi-instance general rules ........................................................................................................... 58

OmniPCX Enterprise - Release : all

OpenTouch Suite for MLE virtualization design guide TBE043

OpenTouch Suite for MLE in virtualized environment, overview [TBE031]

Official documentation package for OXE

Ex : OXE R12.3.1 Documentation package (All languages)

OmniPCX Enterprise - Release : all

VMware is a complex OS which can supported most of guest OS.

OmniPCX Enterprise - Release : all

3.1 Host and hypervisor configuration

3.2 OS GUEST Operating Systems for R12.x releases implemented in these

• Guest operating system

3.3 VMware Tools

VMWare tools is not enabled for release R11 and lower

OmniPCX Enterprise - Release : all

3.4.2 EEGW VM configuration

3.5 OXE-V drivers

OmniPCX Enterprise - Release : all

3.6.2 OMS CPU usage (processor used)

3.6.3 EEGW CPU usage (processor used)

3.6.4 OST64 CPU usage (processor used)

OmniPCX Enterprise - Release : all

3.7.2 OMS, OST64 RAM (exact value of RAM has to be reserved)

3.7.3 EEGW RAM (exact value of RAM has to be reserved)

3.8 Disk usage

3.8.1 OXE-V disk usage

OmniPCX Enterprise - Release : all

3.8.2 OMS, OST64 and EEGW disk usage

3.9 VM virtual resources configuration

4 Limits and VM resource usage in traffic

OmniPCX Enterprise - Release : all

OmniPCX Enterprise - Release : all

OmniPCX Enterprise - Release : all

OmniPCX Enterprise - Release : all

 see table in next slide

OmniPCX Enterprise - Release : all

(*) voicemail disk usage is not taken into account

OmniPCX Enterprise - Release : all

4.7 OST64 VM resource usage

No of Users : (REG Only) 2000 5000 5000-7000

CPU usage in MHz 840 2100 NA

OmniPCX Enterprise - Release : all

Users number: 1000 2000 7000 8000 10000 15000

CPU usage in MHz 150 300 1050 1360 1700 NA

5 ATTRIBUTS AND COMPATIBILITIES FOR OXE VM

OmniPCX Enterprise - Release : all

6.1 ESXI infra 5.5

DISK TYPE IDE SCSI SCSI SCSI

DISK ATTRIBUT Independent - Independent - Independent - Independent -

NIC E1000 E1000 E1000 E1000

MEMORY See 3 chapter See 3 chapter See 3 chapter See 3 chapter

MEMORY YES mandatory YES mandatory YES mandatory YES mandatory

CPU See Appendix See Appendix See Appendix See Appendix

INFRA VMWARE NO YES YES YES

OmniPCX Enterprise - Release : all

DISK TYPE IDE SCSI SCSI SCSI