Virtual Core requirements

If you are installing a virtual Core, you need to ensure that the minimum requirements are met. This section lists the requirements for Core.

Other topics in this section include:

Storage devices
Guaranteed minimum memory and CPU for Core (VMware, Hyper-V)
Minimum specification (VMware, Hyper-V)
Gather required Core information

The following table lists the virtual Core requirements. (Alternative memory and CPU configurations are not covered by the Core product warranty.)

**Table 17.** Virtual Core requirements
Components	Requirements
Hard drive	Ivanti recommends configuring only one hard drive on the virtual machine. System performance is directly related to hard disk drive performance. We recommend using only high-performance tier I storage products.
Backup VMware	Ivanti recommends taking periodic .vmdk backups of your Virtual Appliance as part of your system maintenance. Use VMware VCB or another VMware-supported backup system. A backup of the full virtual disk is recommended; VMware snapshots are not sufficient.
VMware	Download link or package (ISO) from Ivanti Support here: https://support.mobileiron.com/support/CDL.html VMware ESXi 6.5, 6.7, 7.0 64-bit VM Network adapter: E1000 VMXNET 3 VM OS Type: CentOS 7.4 (64-bit) CPU Settings: Shares: Normal Reservation: Match the specification in Guaranteed minimum memory and CPU for Core (VMware, Hyper-V). Limit: Unlimited (maximum assigned) Memory Settings: Shares: Normal Reservation: Match the specification in Guaranteed minimum memory and CPU for Core (VMware, Hyper-V). Alternate reservation: 50% of the specification in Guaranteed minimum memory and CPU for Core (VMware, Hyper-V).* * The alternative memory configuration is not covered by the Ivanti product warranty. Limit: Unlimited (maximum assigned) Boot from BIOS firmware We currently support the LSI logic SAS or Parallel SCSI controllers; para-virtualized controllers are not supported. Alternative memory and CPU configurations are not covered by the Core product warranty
Hyper-V	Download link or package (ISO) from Ivanti Support here: https://support.mobileiron.com/support/CDL.html Microsoft Hyper-V Server 2008, Microsoft Hyper-V Server 2008 R2, or Microsoft Hyper-V Server 2012, Microsoft Hyper-V Server 2012 R2, Microsoft Hyper-V Server 2016 Hyper-V MAC Address: Static allocation Generation 1 VM Boot from BIOS firmware Minimum 4 GB RAM Microsoft Hyper-V Server 2008 requires a legacy network adapter. New features in Microsoft Hyper-V Server 2016 (discrete device assignment, shielded virtual machines, disk encryption, secure boot, etc.) are not supported.
KVM	Download link or package (ISO) from Ivanti Support here: https://support.mobileiron.com/support/CDL.html Minimum configuration of host machine: Quad Core CPU, 2 GHz clock rate 16 GB RAM 8 GB guest memory Performance data for different CPU and RAM and memory configurations is not available. Supported KVM version: QEMU emulator version 2.0.0 (Debian 2.0.0+dfsg-2ubuntu1.22) Core supports only this KVM version, but later versions are compatible. Supported Virtual Machine Manager version: 0.9.5 Core supports only this Virtual Machine Manager version, but later versions are compatible.* Supported Linux distribution: Ubuntu Server version 14.4 (3.19.0-25‑generic #26~14.04.1‑Ubuntu SMP) Core supports only this Linux distribution, but other Linux distributions are compatible.* In the Virtual Machine Manager, when creating a new virtual machine, select Generic for the OS type and the Version. Boot from BIOS firmware. For more information about setting up KVM, see: https://help.ubuntu.com/community/KVM * Ivanti defines supported and compatible as follows: Supported product versions: The functionality of the product and version with currently supported releases was systematically tested as part of the current release and, therefore, will be supported. Compatible product versions: The functionality of the product and version with currently supported releases has not been systematically tested as part of the current release, and therefore not supported. Based on previous testing (if applicable), the product and version is expected to function with currently supported releases. For more information about setting up KVM, see https://help.ubuntu.com/community/KVM.

Storage devices

The following table lists the requirements for storage devices.

**Table 18.** Storage device requirements
Operation	Min IOPS	Bandwidth	90% Operations < xxx mS
Random Read	400	3 MBps	10 mS
Random Write	900*	15 MBps	4 mS

Storage device notes

Ivanti recommends configuring only one storage device per virtual machine.
RAID controller may have to be specifically configured in order to achieve high Random Write IOPS (For example: Disk Cache: Enabled, Default Write: Write Back with BBU).
System performance is directly related to storage device performance. We recommend using only high-performance tier 1 storage products.

Guaranteed minimum memory and CPU for Core (VMware, Hyper-V)

The following table lists the guaranteed memory and CPU requirements for Core.

**Table 19.** Memory and CPU for Core (VMware, Hyper-V)
Maximum Devices	Memory	Virtual CPU / Min Clock Rate	Total Available Storage Capacity	Min Storage IOPS (Random Read)	Min Storage IOPS (Random Write)
< 5,000	8 GB RAM*	Qty 2 / 2.13 GHz processors**	80 to 250GB SAS	400	1000
< 20,000	16 GB RAM*	Qty 4 / 2.13 GHz processors**	250 GB SAS	400	1000
< 50,000	32 GB RAM*	Qty 8 / 2.13 GHz processors**	500 GB SAS	400	1000
< 100,000	64 GB RAM*	Qty 16 / 2.13 GHz processors**	1TB SAS	400	1000

*Guaranteed resource allocation - no ballooning allowed
** Guaranteed resource allocation - no sharing allowed with other VMs

Minimum specification (VMware, Hyper-V)

The following minimum specification does not include significant use of the app store or Docs@Work.

**Table 20.** Minimum specifications
Maximum devices	Memory	Virtual CPUs	Disk
< 500	8 GB RAM*	1 x 2.13GHz processors**	80 to 250GB SAS
Random Write	900*	15 MBps	4 mS

*Guaranteed resource allocation - no ballooning allowed
**Guaranteed resource allocation - no sharing allowed with other VMs

Gather required Core information

Use the following table to gather and record Core information before installation.

**Table 21.** Core Information
Item	Description	Values
Licensing agreement information	The company name, contact person name, and contact person email address for the end-user licensing agreement.
Core Server IP Address	Static IP address for portal access.
External Hostname	Fully-qualified domain name for Core. Do not use an internal hostname. Managed devices must be able to access Core from the Internet.
“enable secret” password	The Core password to be defined for enabling access to Privileged and Configuration modes.
Administrator User Name	The user name to define for the Core Administrator. Do not use root or ha_admin.
Administrator Password	The Core Administrator password must contain the following elements: At least 8 characters. At least 1 alphabetic character. At least 1 numeric character. Cannot have 4 or more repeating characters. Cannot be the same as the user ID. May contain Unicode characters, except for CLI access. Users cannot change a password more than once during a 24 hour period.
Physical Interface	The physical interface to use on the appliance. Enter a or b. You can configure additional physical interfaces later using the System Manager.
IP Address Netmask	The IP address and netmask of the physical network interface.
Default Gateway	The IP address of the router used to forward traffic to destinations outside of the local network or subnet.
Name Server 1, 2, 3	The IP address of a network name server (i.e., DNS server). You must specify at least one name server.
Remote Shell via SSH?	Specifies whether you want to configure remote shell access via SSH.
NTP Server 1, 2, 3	Specifies the IP address of an optional reliable time source. We recommend specifying an NTP server. If you do not, you will have the opportunity to set the system clock and date.