Install > Preinstallation tasks > System requirements for installation > Check SA Cores on VMs requirements (optional)

Check SA Cores on VMs requirements (optional)

SA Cores are certified for VMware VMs running Red Hat Enterprise Linux as the guest operating system.

SA Cores are certified for running inside VMware VMs for all the supported core platforms as guest operating system. The supported versions of the ESXi hypervisors are generally the latest available releases from the vendor. For more information, see SA Support and Compatibility Matrix.

The following topics describe the requirements and instructions for installing an SA Core on a VMware VM.

Supported Hypervisor and Guest Operating Systems

For the list supported Hypervisor and Guest Operating Systems, see SA Support and Compatibility Matrix.

VM CPU and memory requirements

The following table shows the minimum number of CPUs and required memory to run SA Cores on VMs for setting up a laboratory or development environment: 

VM CPU and memory requirements

Number of VMs

Number of CPUs and RAM for each VM

Number of Managed Servers

 

 

 

 

 

4 CPUs
16GB RAM

4 CPUs
16GB RAM

 

1

Infrastructure Component bundle

SA Provisioning bundle

Slice Component bundle

 

960

2

Infrastructure Component bundle

SA Provisioning bundle

Slice 0 Component bundle

Slice 1 Component bundle

2250

Note: SA supports core components installed on VMs only when your VM configurations follow VMware best practices for managing resource allocation and overall workload. You must ensure that other VMs sharing the same ESXi hypervisor do not significantly impact the resources available to the VM hosting the SA Core. If there are performance issues, for troubleshooting purposes, HPE Support may require you to replicate these issues in an environment in which the VM supporting the SA Core is the sole VM active within the ESXi hypervisor.
Note: It is essential that you avoid over-commitment of physical resources (CPU and physical memory) to ensure proper functioning of the VMs. Over-commitment of these resources can lead to performance issues as well as time synchronization issues.

SA satellite memory requirements

The following table provides the minimum number of CPUs and required memory to run SA Satellites on VMs:

Satellite CPU and Memory Requirements

Number of VMs

Number of CPUs and RAM for each VM

Number of Managed Servers

 

 

 

 

 

2 CPUs
2 GB RAM

1

Satellite Components

1500

Hardware performance issues

The hardware requirements for Hypervisors running SA Core VMs can vary based on the following factors:

  • The availability of the physical CPUs and memory in the Hypervisor to support the recommended SA Core VM configuration.
  • The number of VMs running concurrently on the physical server.
  • The number of servers that the SA Core manages.
  • The number and complexity of your concurrent operations.
  • The number of concurrent users who can access the SA Command Center.
  • The number of facilities in which the SA Core operates.

VMware virtual center requirements

Use of the following Virtual Center features with an SA Core installed on a VM has not been validated and could make it difficult for HPE Support to diagnose possible problems with your installation if required:

  • Snapshots
  • Distributed Resource Scheduling (DRS)
  • VMotion
  • Storage VMotion
  • Fault Tolerance
  • High Availability (HA)

HPE is continuing to validate these advanced Virtual Center features and will announce support when available.

SA Core component VMs on SAN or NAS devices

Running SA Core Components on VMs is supported if the VM images are run from a local disk or SAN. Running SA Core Components on VMs is not supported if the VM images are stored on NAS devices.

Installing SA Cores under VMware VMs

SA Core pre-installation requirements, disk space requirements, installation, and post-installation requirements under VMware VMs are the same as those for installation on a physical server. You can use the instructions described in this guide to install an SA Core on an existing VMware VM.