sip-dect knowledge base omm linux server …mitel.helpweb.es/ayudas/documents/sip...

SIP-DECT Knowledge Base

OMM Linux Server Installation AUGUST 2017

DEPL-2044 VERSION 1.11

KNOWLEDGE BASE

TABLE OF CONTENT

1. CENTOS INSTALLATION ...................................................................................... 2

2. CENTOS CONFIGURATION ................................................................................. 7

2.1. Installation of required packets ............................................................................... 7

2.2. FIREWALL CONFIGURATION ............................................................................................. 8 2.3. OMM INSTALLATION ........................................................................................................ 9 2.4. OML INSTALLATION ....................................................................................................... 10 2.5. SELINUX ....................................................................................................................... 10 2.6. NETWORK TIME PROTOCOL ........................................................................................... 10 2.7. VIRTUALIZATION ............................................................................................................ 11 3. ADDITIONAL SERVICES ................................................................................................... 12 3.1. TFTP SERVER .............................................................................................................. 12 3.2. SYSLOG SERVER .......................................................................................................... 13 3.3. DHCP SERVER ............................................................................................................. 13 3.4. FTP SERVER ................................................................................................................ 13 3.5. SNMP SERVER ............................................................................................................ 14 3.6. SYSTEM PERFORMANCE MONITORING ............................................................................ 14 3.7. TIMEZONE MODIFICATIONS ............................................................................................ 14 3.8. TOOLS FOR WINDOWS ® ............................................................................................... 15 4. VIRTUAL MACHINE ENVIRONMENTS ................................................................................ 16 4.1. INTRODUCTION ............................................................................................................. 16 4.2. REDUNDANCY CONFIGURATION ...................................................................................... 17 4.3. PREREQUISITES ............................................................................................................ 17 4.4. REQUIREMENTS ............................................................................................................ 18 4.5. HIGH AVAILABILITY AND FAULT TOLERANCE .................................................................... 18 4.6. LOAD............................................................................................................................ 19 4.7. VMWARE RECOMMENDATIONS ....................................................................................... 20

The information conveyed in this document is confidential and proprietary to Mitel® and is intended solely for Mitel employees and members of Mitel’s reseller channel who specifically have a need to know this information. If you are not a Mitel employee or a Mitel authorizedPARTNER, you are not the intended recipient of this information. Please delete or return any related material. Mitel will enforce its right to protect its confidential and proprietary informationand failure to comply with the foregoing may result in legal action against you or your company.

1 | © MITEL 2017 | SIP-DECT KNOWLEDGE BASE

SIP-DECT KNOWLEDGE BASE | SIP-DECT OMM LINUX SERVER INSTALLATION

This document describes the required configuration steps to install the SIP-DECT applications OMM (OpenMobility Manger) and OML (Locating Server) on CentOS 6 (x86_64). In the first section of this document a basic installation of CentOS 6 (x86_64) on a new computer is described. This is similar when performing a RHEL 6 installation. Afterwards the system configuration after a minimal installation is described. The last section describes requirements to run the OMM and OML in a virtual machine environment, read this chapter first if you use virtual machines. This documentation is only an additional guideline for the installation, please also have a look on the system manuals and release notes for the latest updates and release status information.

REVISION CONTROL INFORMATION

DATE AUTHOR VERSION CHANGES

11.2012 Julian Zelina 1.0 Initial Version

01.2013 Julian Zelina 1.1 Change Aastra Template

04.2013 Julian Zelina 1.2 Add Virtual Machine Environments

11.2013 Julian Zelina 1.4 Add OMM 5.0, firewall ports, java1.7

03.2014 Julian Zelina 1.5 Add OML 4.0SP4 notice

05.2015 Julian Zelina 1.6 Update for SIP-DECT 6.0 and new Brand

09.2015 Julian Zelina 1.7 Add additional services

02.2016 Julian Zelina 1.8 Updates and additional information, ESX 6

07.2016 Julian Zelina 1.9 Update HW Req. SIP-DECT 6.2

03.2017 Julian Zelina 1.10 Improve description and include Win. Tools

08.2017 Julian Zelina 1.11 Add SNMPD, SAR, Timezone modification



1. CENTOS INSTALLATION

This chapter describes how to install a new CentOS 6 with minimal setup. This introduction covers only the minimal requirements to get a CENTOS Server running. CentOS is available on www.centos.org, be aware that multiple ISO images are available. We recommend to use the standard or minimal ISO e.g. CentOS-6.x-x86_64-minimal.iso As minor release versions of CentOS automatically update during the regular update process the latest released CentOS 6 version at that time can be used. Note: The operating system CentOS / RHEL 7.x is not supported so far.

This manual is written for users without linux experience, but for productive environments additional configurations will be required! If your operating system is already installed proceed directly with the next Chapter. Operating system installation:

Insert / mount the CENTOS installation DVD. Configure the PC to Boot from this device and press the ENTER key

The installer asks to check the install DVD. Usually a check is not necessary.



The Setup starts with a “Welcome screen”, click on “next” to proceed.

Select your Language for this Installation. After the installation you can add additional languages.

Select your Keyboard layout.

Specify the storage you like to install CENTOS to. Default: basic storage device (your hard disk)



If the HDD on this computer or virtual machine is empty, the installer shows the following warning. Attention! If the installer doesn’t detect the hard disk on your PC do not proceed!! Maybe you need to install additional drivers first.

Configure your network interfaces here. By default the interface (e.g. eth0 or em0) is configured to use DHCP with IPv4 and IPv6. Configure a Hostname and static IPv4 IP settings. By default the Network interface is not active after startup! Press “Edit” and enable “connect automatically” in the checkbox.



Now select your timezone

Setup the password for the user root. This should be secure and secret! (This is the Administrator login password, not related to the OMM user login.)

Partition Layout If you just want to install only CENTOS on this Computer, leave the config on default and go forward. The installer will create a boot partition as well as a LVM for the swap and file system.



In the default configuration “Minimal”, no graphical user interface (GUI) is available. As this installation type requires the fewest packets, this mode is recommended. Additional required packets can be installed later.

Start the installation with next

Installation is finished, click on “reboot” to reboot.

After the start up a login screen appears. Login with user root and your password for the first configuration.



2. CENTOS CONFIGURATION

2.1. INSTALLATION OF REQUIRED PACKETS

Notice:

It is assumed that this server has (temporary) internet access to download operating system packages and updates to perform the initial installation. If this is not the case, offline yum repositorys e.g. the installation DVDs must be configured.

Run the command “yum update” to install the latest updates first, this will also solve dependency issues with installed packets when installing new packets. yum update

Notice that a restart of services or a reboot of the PC might be required after updating operating system components. To operate the OMM application on CentOS 6 64-bit you need to install 32-bit compatibility packets. yum install glibc.i686 compat-libstdc++-33.i686 compat-gcc-34.x86_64

yum install libstdc++.i686 libzip libzip.i686

The OMM application requires telnet (for the ommconsole) and unzip (for the nstallation) yum install unzip telnet

To operate OML the installation of java and tomcat6 is required. Since SIP-DECT 5.0 Java 1.7 is required for OML. The installation of 32-bit compatibility packets is not required to operate OML. yum install java-1.7.0-openjdk tomcat6

It’s recommended to install system tools for the firewall and network configuration. yum install system-config-network-tui system-config-firewall mc

System tools command usage: - “system-config-network” - terminal program to configure network and DNS. - “system-config-firewall” - terminal program to change firewall configuration - “mc” - terminal program to copy, edit and move files.

We recommend installing minimal services and applications required for the operation of SIP-DECT. Do not install other applications e.g. SIP-Servers as they may interfere. The installation of OML and OMM should not be done on the same machine when operating productive installations.



2.2. FIREWALL CONFIGURATION

By default the Firewall in CentOS is enabled and allows incoming connections via SSH only. To provide access to applications you will need to add firewall rules. Use the terminal tool “system-config-firewall” or edit the firewall settings with a text editor in

/etc/sysconfig/system-config-firewall and apply the changes using “system-config-firewall”

after the changes have been made in the text file. Notice that some server ports can be modified in the OMM configuration e.g. the SIP port range. This requires additional firewall rules for modified ports.

To verify the active firewall rules run “iptables -L –n” Chain INPUT (policy ACCEPT)

target prot opt source destination

ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 stateRELATED,ESTABLISHED

..

ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:443

ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 state NEW udp dpt:69




ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 state NEW udp dpt:5060

..

#Configuration file for system-config-firewall to support OMM, OML

#and optional additional services.

--enabled

--port=12622:tcp

--port=16321:tcp

--port=16322:tcp

--port=5060:udp

--port=5060:tcp

--port=5061:tcp

--port=4060:udp

--port=4060:tcp

--port=4061:tcp

--port=8106:tcp

--port=8107:tcp

--port=123:udp

--port=8080:tcp

--port=38229:tcp

--service=ssh

--service=https

--service=http

--service=tftp

--service=tftp-client

--service=ftp



2.3. OMM INSTALLATION

Copy the OMM installation file (SIP-DECT_<version>.bin) to the hard disk and execute the file. Root permission is required for the installation (use sudo or login as su (super user) e.g. root). [root@omm ~]# sh SIP-DECT_6.2.bin

Unpacking...

Archive: install.omm.1679.zip

inflating: SIP-DECT-OMM-6.2.i586.rpm

inflating: SIP-DECT-HANDSET-6.2.i586.rpm

Preparing... ########################################### [100%]

1:SIP-DECT-OMM ########################################### [100%]

Preparing... ########################################### [100%]

1:SIP-DECT-HANDSET ########################################### [100%]

Done.

If you use a Standby OMM or the Server have multiple network interfaces configure the

OMM configuration file /etc/sysconfig/SIP-DECT before you start the OMM.

Uncomment (remove the #) the line with the parameter OMM_RESILIENCY and configure your OMM1IP:OMM2IP in the following format. #OMM_RESILIENCY="10.10.0.254:10.10.0.253"

To start the OMM run “/etc/init.d/sip-dect-omm start” root@omm ~]# /etc/init.d/sip-dect-omm start

Starting Open Mobility Manager FFSIP: [ OK ]

If the startup fails check the logfiles at /opt/SIP-DECT/spy_trace_<date>.log

To verify the OMM operations run “ommconsole” on the terminal or connect with OMP. root@omm ~]# ommconsole

Trying 127.0.0.1...

Connected to 127.0.0.1.

Escape character is '^]'.

Welcome to the omm console, use ? for a list of possible commands

omm# runtime

2013/11/01 15:17:54.509 ! ALL : process runtime: 17 days, 23:20:20



2.4. OML INSTALLATION

To install OML copy the OML.war file to /var/lib/tomcat6/webapps/

Create an OML database folder on the Linux server.

Verify that java version matching to your release is already installed and running. Since SIP-DECT 5.0 Java 1.7 is required for OML.

If you need to configure the active java version e.g. in case multiple versions are installed run “/usr/sbin/alternatives --config java” to define the active java version.

Configure Tomcat to start on computer startup using “chkconfig --levels 345 tomcat6 on” and start Tomcat afterwards using “/etc/init.d/tomcat6 start” If you like to enable SSL encryption, compression or language settings edit the tomcat configuration files and restart the tomcat service.

2.5. SELINUX

In CentOS default installations Selinux is configured enforcing (apply all policies), this setting may avoid access of certain services as tftp, syslog etc. Observations did not show that Selinux interfere with the OMM application, therefore it can stay enabled. In case you need to run additional services on this machine it may be required to adapt the Selinux policys or matching file system labels. The Selinux configuration file is located in /etc/sysconfig/selinux

To apply changes, restart the computer.

2.6. NETWORK TIME PROTOCOL

For a correct PC time setting, NTP clients or servers can be installed and configured. For a one-time synchronization it is possible to install the NTP client using “yum install ntpdate”. Use the command “ntpdate servername” to sync time (once) with a given server. To run the NTP client on system startup use “chkconfig ntpdate on” or use a cron job for frequent updates. To secure a continuous time syncronisation it is more convenient to install the NTP deamon. To install the NTP deamon run “yum install ntp”, the configuration file is /etc/ntp.conf

[root@omm ~]# yum install ntp

#modify the configuration file located in /etc/ntp.conf

[root@omm ~]# chkconfig ntpd on

[root@omm ~]# service ntpd start

[root@omm ~]# mkdir /var/lib/OML/

[root@omm ~]# chown tomcat:tomcat /var/lib/OML/

[root@omm ~]# java -version

java version "1.7.0_95"



The configuration file /etc/ntp.conf includes a list of NTP servers. Modify the list to your (local) NTP servers if available.

# Use public servers from the pool.ntp.org project.

server 0.centos.pool.ntp.org iburst

server 1.centos.pool.ntp.org iburst

In virtual machines it is recommended to add the parameter “tinker panic 0” to the top of the ntp.conf.

# modification as per http://kb.vmware.com/kb/1006427

# The configuration directive tinker panic 0 instructs NTP not to give up

# if it sees a large jump in time and must be at the top of the ntp.conf file.

tinker panic 0

Notice that in virtual environments the hypervisor (VM server) may be configured to syncronize its time with virtual machines. Also virtual machine tools can influce the time syncronsiation e.g. on startup or when a machine has been suspended. Make sure that time syncronisation is performed by one method. Check the virtual environment documentation and best practice for more details.

2.7. VIRTUALIZATION

If you install the OMM or OML in a virtual environment, make sure the virtual machine tools and drivers are installed on the virtual operating system (Guest / VM). This allows the virtual infrastructure system to monitor and control and optimize the virtual machine operating system.

The dialog to install this software can be initiated in the User Interface of the virtual machine tool. In this example VMware® Tools is installed from a vSphere® Client: Select Install VMware Tools in the VMware® Client,

this will “insert” a CD with the VMware® Tools installer into the virtual operating system. Execute the following commands to mount this CD and install VMware® Tools:

yum install perl

mkdir /mnt/cdrom

mount /dev/cdrom /mnt/cdrom/

tar zxpf /mnt/cdrom/VMwareTools-*

cd vmware-tools-distrib/

./vmware-install.pl

Creating a new VMware Tools installer database using the tar4 format.

Installing VMware Tools.

….. Follow the default recommendations from the installer to finish the installation



3. ADDITIONAL SERVICES

This section describes the installation off additional services which can be required to operate a SIP-DECT system therefore some basic configuration examples are provided in this section. Please choose carefully which services and applications you install on the same machines / platforms. Especially take into consideration when installing multiple services on the same machine:

- Expected load (CPU, memory, network) as high load increases delays or may influence services. - Availability of services (impact if a machine fails, need to distribute services to multiple machines) - Redundancy (do a service needs to be configured redundant to reduce the impact of a outage)

3.1. TFTP SERVER

The TFTP server can be used for software and configuration file transfers. RFPs offer to use a list of up to 3 TFTP Servers for the software download for failover and load distribution. Using TFTP over WAN connections is slow, consider using a faster protocol as HTTP/FTP in such scenarios. To install a TFTP server run the following commands: [root@omm ~]# yum install tftp*

[root@omm ~]# /sbin/chkconfig --level 345 xinetd on

[root@omm ~]# /sbin/chkconfig --level 345 tftp on

[root@omm ~]# /etc/init.d/xinetd restart

The default TFTP server root location is /var/lib/tftpboot/ place your files e.g. iprfp3G.dnld into this folder. When Selinux is enabled the files are not accessible as the SELinux security context is not included. To set a correct label execute the command restorecon and verify the result using the ls –Z output. [root@omm ~]# restorecon -v /var/lib/tftpboot/*

restorecon reset /var/lib/tftpboot/iprfp2G.tftp context…

[root@omm ~]# ls -Z /var/lib/tftpboot/

-rw-r--r--. root root unconfined_u:object_r:tftpdir_rw_t:s0 iprfp2G.tftp

-rw-r--r--. root root unconfined_u:object_r:tftpdir_rw_t:s0 iprfp3G.dnld

By default the TFTP server is not writeable. It may be required to allow the upload of backups and coredumps. If you need to modify the TFTP server to allow write access edit the configuration file /etc/xinetd.d/tftp Edit the line “server_args = -s /var/lib/tftpboot” to include a “-c” as parameter

service tftp

{…

server_args = -c -s /var/lib/tftpboot

…}

Restart the TFTP server, enable write access in Selinux and create a writeable folder in the tftp directory. [root@omm ~]# /etc/init.d/xinetd restart

[root@omm ~]# setsebool -P tftp_anon_write 1

[root@omm ~]# mkdir /var/lib/tftpboot/corefiles

[root@omm ~]# chmod 777 /var/lib/tftpboot/corefiles



3.2. SYSLOG SERVER

A syslog server can be used to receive diagnostic events e.g. from the base stations. To enable the syslog server edit the file /etc/rsyslog.conf and modify the following lines: # Provides UDP syslog reception

$ModLoad imudp

$UDPServerRun 514

Restart the rsyslog service to apply the new configuration [root@omm ~]# /etc/init.d/rsyslog restart

Be aware that the configured port must be open in the firewall which is not default e.g. add port 514 UDP. By default the syslog messages are written to /var/log/messages

3.3. DHCP SERVER

The DHCP server configuration is described in the SIP-DECT Knowledge base: DHCP configuration.

[root@omm ~]# yum install dhcp

#perform the required dhcpd.conf configuration

[root@omm ~]# chkconfig dhcpd on

[root@omm ~]# service dhcp start

3.4. FTP SERVER

The FTP server can be used to transfer software and configuration files. This protocol is usually faster than TFTP, especially when using WAN connections. FTP can be used by most OMM services. Base stations can perform e.g. software downloads via FTP. This requires to configure the RFP configuration file server (ipdect.cfg / <mac>.cfg) via OM Configurator or DHCP. The FTP server than needs to provide the ipdect.cfg containing the Software URL parameter: “OM_SwImageUrl=ftp://server/iprfp3G.dnld”, along with the software files. To perform the FTP Server installation and startup run the following commands: [root@omm ~]# yum install vsftpd

#perform the vsftpd.conf configuration if required.

[root@omm ~]# chkconfig vsftpd on

[root@omm ~]# service vsftpd start

In this default configuration the vsftpd FTP server is configured to allow anonymous FTP connections to perform download from files located in the FTP server directory: /var/ftp/pub/ To restrict access to user logins or to allow the upload of files, configure the vsftpd configuration file located in /etc/vsftpd/vsftpd.conf (restart the service to apply changes). Notice:

- SElinux by default prevents users to access the home directory. (setsebool -P ftp_home_dir 1) - For security reasons user access can be limited to home dir. (vsftpd.conf: chroot_local_user=YES) - FTP by default is not encrypted, TLS can be deployed to secure the connection. - By default the FTP port is blocked in the firewall configuration (add --service=ftp)



3.5. SNMP SERVER

A SNMP Server can be configured to allow the monitoring of this server by a network monitoring system like Mitel Performance Analytics, Incinga or other available applications. The configuration have to include a community string and IP address/subnet which is allowed to query the server.

[root@omm ~]# yum -y install net-snmp net-snmp-utils

#perform the configuration in the file /etc/snmp/snmpd.conf

# snmpd.conf sample file - /etc/snmp/snmpd.conf

# Your Location

syslocation Server Room

# Your Contact

syscontact Sysadmin (root@localhost)

# SNMP community string (e.g. public) to access your system

# and ip address / range from which SNMP requests are allowed.

# rocommunity public 127.0.0.1

# rwcommunity mysecret 127.0.0.1

rocommunity public 10.10.1.0/24

[root@omm ~]# chkconfig snmpd on

[root@omm ~]# service snmpd start

[root@omm ~]# system-config-firewall #Open the firewall port 161/udp

3.6. SYSTEM PERFORMANCE MONITORING

Multiple tools to monitor the system performance are available. “sar” is a common application to see the system resource allocation over a certain time period. Use “man sar” for more handling details.

[root@omm ~]# yum install sysstat

[root@omm ~]# /etc/init.d/sysstat start

[root@omm ~]# chkconfig sysstat on

3.7. TIMEZONE MODIFICATIONS

In case the timezone need to be changed on a running system, no UI is available as during the installation. The following steps perform the required actions to change the timezone from terminal.

1. display current time

[root@omm ~]# date

2. find your timezone label (location of the timezone file)

[root@omm ~]# ls -R /usr/share/zoneinfo/

3. Backup / Move your current timezone settings

[root@omm ~]# cp /etc/localtime /root/localtime.old

4. Link the new timezone with your correct new label.

[root@omm ~]# ln -s /usr/share/zoneinfo/Europe/Dublin /etc/localtime

5. Verify that the date is matching.

[root@omm ~]# date



3.8. TOOLS FOR WINDOWS ®

To access and manage a Linux Server from a Windows ® Operating System, additional tools are usually required to access the linux server and perform operations as a file transfer. This section introduces some common tools available for free which help with common tasks.

SSH Client (remote terminal)

SSH clients allow to connect into a linux server using an encrypted TCP connection. In CentOS a SSH server is running by default. Login with a configured user e.g. root and perform operations like the terminal instructions provided in this document. Software: PuTTY

SSH / SCP Client (file transfer and editor)

SSH subsystems can also be used to transfer files. As it is a common request to transfer and edit files, a tool which provides an GUI simplify the handling. With such client’s, files can be transferred between the local operation system and the remote server. Some clients also provide an editor to open and edit configuration and log files on the remote server directly. Software: WinSCP, Filezilla



4. VIRTUAL MACHINE ENVIRONMENTS

OMM and OML can also operate in a hardware virtualized environment. Mitel has verified the operation of SIP-DECT OMM and OML running as virtual machines in a VMware® vSphere/ESXi 5 and 6 infrastructure with advanced features for hardware redundancy. This section describes the basic conditions and requirements for such a setup. The installation of the VMware® environment should be performed by trained engineers following the latest guidelines and recommendations of VMware®. Mitel does not supply any VMware® or operating system software with SIP-DECT. The solution described in this document runs on top of a VMware® infrastructure and therefore all VMware® requirements for such a scenario must be in place before start.

4.1. INTRODUCTION

In virtual environments one physical server (host server / machine) hosts multiple independent virtual machines (VM / guest machine). To operate multiple virtual machines on the same (shared) hardware environment a hypervisor is installed as an abstraction layer on the host server platform. The virtual machines can run independent operating systems and applications like real computers. Benefit of this technology is the reduction of hardware, operational and maintenance costs.

Virtualization technology can also be used to increase the availability and reliability of services. Depending on the customer requirements this usually requires a more complex setup for the infrastructure and components. Detection and reaction of hardware / software (e.g. operating system freeze) faults are handled by the Hypervisor(s).

Traditional Hardware Virtualizied Environment



4.2. REDUNDANCY CONFIGURATION

Compared to a basic VMware host server (for minimal setup) a more complex setup is required for high availability and reliability scenarios. In such scenario all host servers are connected to

- the local productive network to

provide the services (LAN)

- to a network storage which provides the

virtual machine

hard disk files (SAN)

- to a management network

for transfer of information / VMs.

(e.g. for VMotion)

- to mirror virtual machine states

for fault tolerance (if FT is used)

Fault scenario descriptions - If a hardware server fails other server(s) can startup virtual machines after a timeout.

In this case there is a service downtime until the VM did start up again. e.g. VMware® High Availability (HA)

- Virtual Machines (i/o states) can be mirrored in real time to the other server,

if one hardware server fails the second server take over and keep the VM running. e.g. VMware® Fault Tolerance (FT)

4.3. PREREQUISITES

• A certified VMware ESXi 5 or 6 host (minimum) or a vCenter (Datacenter) solution.

• The vSphere Client installed on a workstation or the WEB client is deployed.

• RHEL 6 or CentOS 6 Installation DVD image (as ISO files)

• SIP-DECT installation files and licenses

• Good knowledge of VMware vSphere/ESXi.

• Good knowledge of RHEL / CentOS and SIP-DECT installation.

• In case the virtual disk is located on a network storage (SAN) low read/write latency is required.



4.4. REQUIREMENTS

For virtualization, we require a VMware® certified server infrastructure which is configured according to the VMware® requirements and best practices. The Virtual Machines for the OMM and OML should be created with the following values.

Platform: VMware® VSphere/ESXi

CPUs: 1 Socket with 2 cores (each minimum 2 GHz) To use VMware Fault Tolerance (FT) see notes below.

RAM: 4 GB (2GB for OML)

Hard disk: 20 GB

Network: 1 Gigabit Ethernet, NIC: VMXNET3

VM Version: 8 (features of higher version usually not required)

Resource Allocation:

CPU: 1000 MHz reserved for the active OMM

4.5. HIGH AVAILABILITY AND FAULT TOLERANCE

In addition to the Standby OMM function which provides a failover in case the OMM application (or hardware) fails, VMware built in features can be used for additional hardware redundancy. We recommend using High Availability (HA) only for fault recovery scenarios. As the “primary” OMM function move between the OMM1 and OMM2 virtual machines, VMware cannot determine which VM can be temporary turned off without service interruption. Do not use HA for automatic load distribution scenarios with the SIP-DECT VMs i.e. for load distribution or power management, as the service may be interrupted. Fault Tolerance (FT) can be used to keep the OMM function alive if the VMware host server hosting this VM fails. In this case another host server which runs a mirror of this VM continues the VM operation in real time. In VSphere 5 FT was limited to one vCPU core on the virtual machine which depending on the host machine might lead to performance reductions in certain load scenarios e.g. startup. Since VSphere 6 multiple cores are supported by the platform, check the FT guides for further information. A choice between performance e.g. HA + OMM Resiliency and availability e.g. FT + OMM Resiliency needs to be taken in consideration to match the requirements in a customer project.



4.6. LOAD

The CPU and Network load of the OMM application depend on various parameters e.g.

• the number and type of terminals and base stations

• the number of calls and handovers

• the call server (e.g. featured Mitel PBX with display updates)

• connected applications (e.g. OMP, Messaging, Locating, Provisioning, ..)

Important:

During the OMM startup or failover, system updates and big configuration changes the system load will increase up to the hardware limits e.g. the CPU core(s). To make sure the startup succeeds and the real time services remain available in such peak situations, sufficient resources have to be available on the host machine at all time. After the initial startup phase the load will decrease to a lower level. (see below) We recommend reserving at minimum 1000 MHz for the virtual machine to cover the minimal requirements for a successful startup and peak traffic situations. With more CPU resources available the startup can be up to 50% faster. To test this scenario, restart the OMM Application when all RFPs and Handsets are connected. Increase the reservation according to your installation if required.

The following tables list different load calculations using a simple system configuration in operative state. This is just a guideline as the load per scenario will differ depending of various parameters.

Standard call load scenarios

Users Calls/sec. Calls/hour CPU (MHz) Network avg. (kbit/s)

2000 4 14.400 400 1900

3000 5 18.000 500 2000

4000 7 25.200 600 2400

5000 9 32.400 900 4400

10000 17 70.000 1000 8800

High call load scenarios

Users Calls / sec. Calls/hour CPU (MHz) Network avg. (kbit/s)

4500 22 80.000 1000 7200

4500 44 160.000 1500 12000

10000 55 200.000 3300 32000



4.7. VMWARE RECOMMENDATIONS

Please read at least the following VMware reference documents:

• VMware vSphere Basics Guide - ESXi

• vSphere Availability ESXi

• High Availability Deployment Best Practices

• Protecting Mission-Critical Workloads with VMware Fault Tolerance

• VMware Fault Tolerance Recommendations and Considerations on VMware vSphere

• Timekeeping and Timekeeping best practices for Linux Guests

• Performance Best Practices for VMware vSphere

Please, always check the latest products documentation.

Requirements for VMware High Availability and Fault Tolerance setup:

• SAN (Storage Area Network) and Network requirements for High Availability

according to VMware specifications.

• VMware vSphere, Hypervisor: ESXi

• VMware vCenter

• VMware vMotion

• VMware High Availability

• VMware Fault Tolerance (for Fault Tolerance only)

SAN environment and multiple LAN segments are required by VMware in order

for the HA / FT option to be deployed. Refer to the latest VMware packaging options to

determine the VMware software editions that best fit the requirements.

The VMware vSphere standard edition should include HA and vMotion.

The VMware vSphere enterprise editions should include HA/FT and vMotion.

VMware vCenter is usually ordered separately and is required to set this environment in place.

Mitel strongly recommends that partners/customers always check the latest High Availability/FT requirements

with a qualified VMware technical representative.



Recommendations and limitations with VMware Fault Tolerance

The VMware Fault Tolerance has some limitations/recommendations that need

to be taken in consideration before implementing such a solution.

As VMware requires that vSphere HA/FT operate in a single physical datacenter,

Mitel validation of HA/FT has been carried out in this environment.

It is recommended that no more than four Primary and Secondary VMs be placed onto the same ESXi host.

Only virtual machines with a single vCPU are compatible with Fault Tolerance

Please note that data backup and mayor configuration changes in a big system can affect the system

performance, so Mitel´s recommendation is to make it during low traffic hours.

sip-dect knowledge base omm linux server …mitel.helpweb.es/ayudas/documents/sip...

Documents