Server specifications

Before installing the Mividas Installer VM, please review the recommended server specifications and prerequisites below.

Note: For Mividas Rooms installations, consider additional storage for firmware files. Each firmware version may require an additional 1-2 GB. We recommend thick disk provisioning for virtual machines; thin provisioning may work but should be used cautiously.

We recommend the following configurations based on expected traffic for production use on a single server/VM. For installations exceeding the requirements below, please contact Mividas for a customized deployment.

Normal Traffic Installation

Up to 1,000 concurrent call participants.
Up to 1,000 managed video conference systems/devices.

Specifications
4 vCPU
8 GB RAM
100 GB SSD/SAN storage ¹
1-2 NICs	(behind a firewall/reverse proxy)

^{1. For Mividas Rooms installations, you need to consider the disk space of firmware files. Each firmware version may require 1-2 GB of additional storage space.}

High Traffic Installation

1,000-2,000 concurrent call participants.
1,000-2,000 managed video conference systems/devices.

Specifications
8 vCPU
16 GB RAM
200 GB SSD/SAN storage ¹
1-2 NICs	(behind firewall/reverse proxy)

^{1. For Mividas Rooms installations, you need to consider the disk space of firmware files. Each firmware version may require 1-2 GB of additional storage space.}

Prerequisites

Before deploying, ensure the following are available:

Hostname and SSL Certificate for each active function:
- Mividas Core/Mividas Rooms Management Interface.
- Mividas Meeting Portal and Mividas Outlook Add-In.
- (Optional) Separate hostname for video endpoint API requests (for access control).
Firewall Configuration: Open required ports according to the Network Port Requirements.

Optional Configurations

LDAP Authentication:
- Service account with read access.
- LDAP filter for Mividas Core/Mividas Rooms users.
- Optional group names for admin and superuser permissions.
- LDAP filter for Mividas Meeting Portal users, with optional admin group permissions.
Mividas Portal – SAML SSO Authentication:
- Entity ID starting with https:// and followed by the portal FQDN.

FAQ

Here are some frequently asked questions (FAQs) to help you find the answers you’re looking for.

How do i clean /var/log if its full?

To clean up the /var/log directory when it’s full, you can follow these steps using SSH or the Mividas Installer console:

Check and Identify Large Files

Identify the largest folders in /var/log:

sudo du -xh /var/log | sort -h | tail -n40

List files by size within the /var/log and /var/log/docker/ directories to locate the largest log files:

ls -shSr /var/log/
ls -shSr /var/log/docker/

Delete Unnecessary Log Files

Delete specific old log files one at a time:

sudo rm /var/log/<file_name>

Bulk delete compressed log files:

sudo rm -f /var/log/*.log.[1-4].gz

Run Hard Drive Cleanup from the Mividas Installer Console

Access Hard drive cleanup options in the Mividas Installer console:

Debug logs/raw call data: Remove old debug logs and raw call data.
Old versions: Remove old versions of components or software.

Clean Up Docker Resources

Remove unused Docker images if they’re no longer needed:

sudo docker image prune -f

Note: Only perform Docker cleanup when all Mividas components are active and running. If components are missing or inactive, this can lead to further cleanup or redeployment needs, particularly for offline systems.

Remove all unused Docker resources (images, containers, networks):

sudo docker system prune -f

Clean up any Docker resources that are not currently in use:

sudo docker system prune -af

By following these steps, you can manage storage in /var/log effectively without compromising system stability.

How do i extend the disk for Mividas?

To extend the disk for Mividas, follow these steps:

Close the Mividas Installer – Stop any ongoing operations in the Mividas Installer.
Extend the Disk in VMware – Use the VMware interface to allocate additional storage space to the virtual machine where Mividas is installed.
Restart Mividas – Start the Mividas virtual machine after resizing the disk. The system will automatically detect and configure the new disk size, typically within 10-15 minutes.

These steps allow the Mividas environment to recognize and use the increased disk space without additional manual configurations.

Explore Our Topics

Server specifications