Virtualizing SwyxWare using VMware (kb4303)
The information in this article applies to:
- SwyxWare 11.00
- SwyxWare 11
- SwyxWare 2015 R40.3.0
- SwyxWare 2015 R40.2.0
- SwyxWare 2015 R40.1.0
- SwyxWare 2015 R40.0.0
- SwyxWare 2015 R30.5.0
- SwyxWare 2015 R30.4.0
- SwyxWare 2015 R3.2.2
- SwyxWare 2015 R3.2
- SwyxWare 2015 R3.1
- SwyxWare 2015 R3
- SwyxWare 2013 R6
- SwyxWare 2015 R2
- SwyxWare 2015
- SwyxWare 2013 R5
- SwyxWare 2013 R4
- SwyxWare 2013 R3
- SwyxWare 2013 R2
- SwyxWare 2013
- SwyxWare 2011 R2
- VMware VSphere 4.0 (ESXi 4.0)
- SwyxWare 2011
This article describes the requirements and configuration which is needed for virtualizing SwyxWare (starting with version 2011 and newer) using VMware.
The information from this article can be applied to an Hyper-V system as well.
For virtualization of SwyxWare (Version ≥ 2011) using VMware the following requirements must be fulfilled:
- VMware Version: min. VSphere 4.0 (ESXi Server 4.0 and later)
- Operating System: min. Windows Server 2008 R2 or newer, but matching a supported OS for your SwyxWare version, please see Supported Operating Systems (Overview) (kb4094)
- SwyxWare Version: min. SwyxWare 2011 or newer
- To realise the interconnection of SwyxWare a separately installed SwyxGate (additonal physical server with SX2 ISDN boards) or SIP-Gateway (e.g. SwyxConnect 8xxx, 6xxx, 5xxx or 17xx) or otherwise a SIP- or ENUM-trunk is needed, because SwyxGate is not supported to be installed in a virtual machine.
Create a virtual machine (VM) using the following configuration steps:
- Use Virtual Machine Version 7.0 (ESX Server Version 4.0 and later)
- Guest operating system Windows Server 2008 R2 (64-bit) or newer, but matching a supported OS for your SwyxWare version, please see Supported Operating Systems (Overview) (kb4094)
Configure the required resources for the VM on the basis of KB-article Hardware Recommendations for SwyxWare (Overview) (kb2155)
- e. g. 2 virtual CPU and 2 GB RAM
Create a static harddisk (Thick Provisioning).
- It is recommended to create a separate harddisk for the SwyxWare tracing.
After the VM is created successfully it needs to be higher prioritised than other VMs on the same host.
- Increase the CPU shares for the SwyxWare VM by setting the share value to ‚high‘.
- Increase the Storage shares for the SwyxWare VM by setting the share value to ‚high‘.
As result of this prioritisation it is allowed to use one SwyxWare per VM-host only! (because otherwise such a prioritisation is not possible). SwyxWare with installed option pack Standby is an exception to this, where the prioritisation needs to be set up for both SwyxWare VMs (Master and Standby). But in this case only one SwyxWare VM will be active and therefore the general requirement is fulfilled, too.
But to avoid a single point of failure it is recommended to run the Master and Standby VM at different physical VMware hosts.
Recommended settings and basic conditions using VMware:
- Check your system for the correct settings of date and time to ensure the registration of clients and phones. It is advisable to manage the VMs operating system via MS Active Directory Domains.
- Use the performance monitoring and the features of VCenter to check that the configured resources for the VM are sufficient.
- Define alarms and configure the required report email address to be informed about VM resource lacks.
- Itt has been proved to be useful using the VMXNET3 driver as a paravirtualized NIC. The standard network card driver for Intel e1000 shows bad behaviour in high load situations which may lead to problems in signaling and registration.