Proxmox VE Standard Setup

The tables below show the MX-ONE 7.x requirements for RAM Memory, CPU or vCPU, the clock speed and the required disk space when running combinations of the following MX-ONE applications: Service Node (SN), Service Node Manager (SNM), Provisioning Manager (PM), Database (Cassandra) and Media Server (MS). In some cases, Mitel strongly recommend running Provisioning Manager, Cassandra and/or the Media Server applications in different servers/VMs to avoid performance constraints.

Raid Controller must have at least 1 GB cache.

For the database disks, SSD disks are highly recommended to avoid performance issues both in bare metal or virtualized systems.

Service Node 1 with MX-ONE Applications

Minimum system requirements for Service Node 1 and Service Node standby, including other MX-ONE applications Service Node Manager, Provisioning Manager, Database (Cassandra) and Media Server.

Provisioning Manager must be installed in stand-alone VM for systems above of 2000 users.

The table below includes Service Node Manager, Database (Cassandra) and Media Server.

Service Node 1 and Service Node 1 Standby with Applications
Standard Proxmox VE
Number of Devices	Memory (GB)	CPU	CPU	Disk	Disk	Application	Max Traffic
Max SIP Devices Capacity	Minimum Memory required/reserved in GB per VM	Minimum CPU/vCPU required	Minimum MHz required/reserved	Disk Size (GB)	Large System (more than 3 servers) (GB)	Type of Application	Calls per Second
500	8	2	2000	100	120	SN, SNM, Cassandra, and Media Server	1.00
1000	8	3	2500	100	120	SN, SNM, Cassandra, and Media Server	2.00
2500	10	4	3500	100	120	SN, SNM, Cassandra, and Media Server	5.00
5000	12	6	5500	100	120	SN, SNM, Cassandra	10.00
7500	14	6	6000	100	120	SN, SNM, Cassandra	15.00
10000	16	8	6000	150	180	SN, SNM, Cassandra	20.00
15000	20	8	8000	150	180	SN, SNM, Cassandra	30.00

The table below includes Service Node Manager, Provisioning Manager, Database (Cassandra) and Media Server.

Service Node 1 and Service Node 1 Standby with Provisioning Manager
Standard Proxmox VE
Number of Devices	Memory (GB)	CPU	CPU	Disk	Disk	Application	Max Traffic
Max SIP Devices Capacity	Minimum Memory required/reserved in GB per VM	Minimum CPU/vCPU required	Minimum MHz required/reserved	Disk Size (GB)	Large System (more than 3 servers) (GB)	Type of Application	Calls per Second
500	8	3	2500	100	120	SN, SNM, Cassandra, and Media Server	1.00
1000	10	4	3000	100	120	SN, SNM, Cassandra, and Media Server	2.00

Other Service Nodes with MX-ONE Applications

Minimum system requirements for Other Service Nodes and other Service Nodes standby, including other MX-ONE applications Provisioning Manager, Database (Cassandra) and Media Server.

Provisioning Manager must be installed in stand-alone Proxmox VE for systems above of 2000 users.

The table below includes Service Node Manager, Database (Cassandra) and Media Server.

Other Service Node and Other Service Node Standby with Applications
Standard Proxmox VE
Number of Devices	Memory (GB)	CPU	CPU	Disk	Disk	Application	Max Traffic
Max SIP Devices Capacity	Minimum Memory required/reserved in GB per VM	Minimum CPU/vCPU required	Minimum MHz required/reserved	Disk Size (GB)	Large System (more than 3 servers) (GB)	Type of Application	Calls per Second
500	6	2	2000	100	100	SN, Cassandra, and Media Server	1.00
1000	8	3	2500	100	100	SN, Cassandra, and Media Server	2.00
2500	10	4	3500	100	100	SN, Cassandra, and Media Server	5.00
5000	12	6	5500	100	100	SN, Cassandra	10.00
7500	12	6	6000	100	100	SN, Cassandra	15.00
10000	14	8	6000	100	100	SN, Cassandra	20.00
15000	16	8	8000	100	100	SN, Cassandra	30.00

The table below includes Service Node Manager, Provisioning Manager, Database (Cassandra) and Media Server.

Other Service Node and Other Service Node Standby with applications and Provisioning Manager
Standard Proxmox VE
Number of Devices	Memory (GB)	CPU	CPU	Disk	Disk	Application	Max Traffic
Max SIP Devices Capacity	Minimum Memory required/reserved in GB per VM	Minimum CPU/vCPU required	Minimum MHz required/reserved	Disk Size (GB)	Large System (more than 3 servers) (GB)	Type of Application	Calls per Second
500	8	3	2500	100	100	SN, PM, Cassandra, and Media Server	1.00
1000	10	4	3500	100	100	SN, PM, Cassandra, and Media Server	2.00

The table below includes only Provisioning Manager.

Other Service Node and Other Service Node Standby with Provisioning Manager
Standard Proxmox VE
Number of Devices	Memory (GB)	CPU	CPU	Disk	Disk	Application	Max Traffic
Max SIP Devices Capacity	Minimum Memory required/reserved in GB per VM	Minimum CPU/vCPU required	Minimum MHz required/reserved	Disk Size (GB)	Large System (more than 3 servers) (GB)	Type of Application	Calls per Second
500	6	3	2500	100	100	SN, PM	1.00
1000	8	4	3500	100	100	SN, PM	2.00

Other Service Nodes

Minimum system requirements for Other Service Nodes (Service Node).

Other Service Node and Other Service Node Standby
Standard Proxmox VE
Number of Devices	Memory (GB)	CPU	CPU	Disk	Disk	Application	Max Traffic
Max SIP Devices Capacity	Minimum Memory required/reserved in GB per VM	Minimum CPU/vCPU required	Minimum MHz required/reserved	Disk Size (GB)	Large System (more than 3 servers) (GB)	Type of Application	Calls per Second
500	6	2	2000	100	100	SN	1.00
1000	8	3	2500	100	100	SN	2.00
2500	8	4	3500	100	100	SN	5.00
5000	10	4	5500	100	100	SN	10.00
7500	12	4	6000	100	100	SN	15.00
10000	14	6	6000	100	100	SN	20.00
15000	16	6	8000	100	100	SN	30.00

Media Server Standalone

In larger networks with lots of SIP end-point traffic, it may be beneficial to have the Media Server (MS) reside in a separate server or Proxmox VE to avoid putting load on the Service Node. Also, if there is a need to have more than one Media Server controlled by the same MX-ONE Service Node, the other MS instances would have to run in separate Linux server / Proxmox VE, although managed by the same Service Node.

Minimum system requirements for Media Server standalone.

Media Server Standalone
Standard Proxmox VE
RTP	Memory (GB)	CPU	CPU	Disk	Application
Number of RTP channels	Minimum Memory required/reserved in GB per VM	Minimum CPU/vCPU required	Minimum MHz required/reserved	Disk Size (GB)	Type of Application
500	6	2	2000	100	Media Server
1000	8	3	2500	100	Media Server
2000	10	4	4000	100	Media Server

Provisioning Manager Standalone

This configuration with the Provisioning Manager (PM) on a separate standalone server/Proxmox VE from Service Node 1 is optional and recommended for networks with more than 2000 users. This is to avoid creating load on the SN itself, in particular when things like back-up or bulk provisioning are done. It is also the preferred configuration when a customer has more than one MiVoice MX-ONE sub-system (multiple networked MX-ONE systems) to manage, as it removes any dependency any given system. This is especially important when the customer’s MX-ONE systems are running different SW versions, as provisioning manager can support connecting and managing different MX-ONE versions concurrently. Additionally, in this setup, the PM software version can be kept to the latest release without affecting any given MX-ONE system in the network.

Minimum system requirements for Provisioning Manager standalone.

Provisioning Manager Standalone
Standard Proxmox VE
Number of Users	Memory (GB)	CPU	CPU	Disk	Application
Number of Users managed	Minimum Memory required/reserved in GB per VM	Minimum CPU/vCPU required	Minimum MHz required/reserved	Disk Size (GB)	Type of Application
500	4	2	1000	100	PM Standalone
1000	4	2	1000	100	PM Standalone
2500	6	2	1000	100	PM Standalone
5000	6	4	3500	100	PM Standalone
7500	6	4	3500	100	PM Standalone
10000	8	4	3500	100	PM Standalone
15000	8	4	3500	100	PM Standalone
30000	12	6	4000	100	PM Standalone
50000	16	6	4000	100	PM Standalone
70000	20	6	4000	100	PM Standalone
100000	24	6	4000	100	PM Standalone

Database Standalone Or Large Co-located Databases

This configuration with the Cassandra DB on a standalone server from the SN is optional and typically only used for larger networks to avoid load on the SN itself or if there is a desire to connect more than one Service Node to the same database. Note that this will increase the IP interface load, so 10 Giga Ethernet cards are recommended in database standalone servers. For the database, SSD disks are highly recommended to reduce latency.

In virtualized systems, it is highly recommended to create database (Cassandra) servers in local SSD disks.

Minimum system requirements for Database standalone or large co-located databases.

Database (Cassandra) Standalone
Standard Proxmox VE
Number of Users	Memory (GB)	CPU	CPU	Disk	Application
Number of SIP Extensions with 40 Keys	Minimum Memory required/reserved in GB per VM	Minimum vCPU required	Minimum MHz required/reserved	Disk Size (GB)	Type of Application
500	4	2	2000	100	Cassandra Standalone
1000	4	3	2000	100	Cassandra Standalone
2500	4	3	2000	100	Cassandra Standalone
5000	7	3	3000	100	Cassandra Standalone
7500	7	3	3500	100	Cassandra Standalone
10000	9	4	4000	100	Cassandra Standalone
15000	12	4	5000	100	Cassandra Standalone
30000	15	4	5000	100	Cassandra Standalone
50000	24	8	5000	100	Cassandra Standalone
70000	28	8	5000	100	Cassandra Standalone
100000	32	8	6000	100	Cassandra Standalone

Note:

If a system includes integrated DECT phones, the calculations will need to be adjusted compared to systems with only SIP extensions due to roaming activities. For more information, refer to Cordless Phone Installation Planning (5/1531-ANF90114).

The load from integrated DECT roaming is much heavier than a SIP reregistration, but one roaming is less heavy than a basic call. The heaviness of a roaming depends on the type of roaming and can range from 0.1 to 0.5 of a basic call. However, there can be many roamings for one user.

For instance, in a highly mobile DECT system, DECT users can roam 30-90 times per day or more, whereas really mobile users can do several thousand roamings per day. Suppose an example of 30 roamings per day for one user, where 50% of the roamings are heavier (0.5 call) and 50% are less heavy (0.1 call). In that case, the load from this integrated DECT terminal (call + roamings) should at least be equal to the load from nine SIP terminals (calls plus re-registrations).

In a standard DECT system, a terminal on average roams less frequently than in a highly mobile system, but assume, for example, 10 times per day. Suppose 50% of the roamings are heavier (0.5 call load) and 50% are less heavy (0.1 call load). Calculate with approximately five times more roaming events than call events (example based on Mobility Logging data). The load from a DECT terminal (call + roamings) should at least be equal to the load from a SIP terminal (call + reregistrations). For the roamings, add an equal amount to the load of three SIP users for one integrated DECT user, which equals the sum of four SIP users.

↑