Virtual infrastructure and hardware system requirements
Suggest changes
PDFs
Depending on whether you are installing Unified Manager on virtual infrastructure or on a physical system, it must meet minimum requirements for memory, CPU, and disk space.
The following table displays the values that are recommended for memory, CPU, and disk space resources. These values have been qualified so that Unified Manager meets acceptable performance levels.
| Hardware configuration | Recommended settings | ||
|---|---|---|---|
RAM |
12 GB (minimum requirement 8 GB) |
||
Processors |
4 CPUs |
||
CPU cycle capacity |
9572 MHz total (minimum requirement 9572 MHz) |
||
Free disk space |
VMware:
|
||
Red Hat or CentOS: 150 GB, where the capacity is allocated as follows:
|
Windows: 150 GB, where the capacity is allocated as follows:
|
Unified Manager can be installed on systems with a small amount of memory, but the recommended 12 GB of RAM ensures that enough memory is available for optimal performance, and so that the system can accommodate additional clusters and storage objects as your configuration grows. You must not set any memory limits on the VM where Unified Manager is deployed, and you must not enable any features (for example, ballooning) that hinder the software from utilizing the allocated memory on the system.
Additionally, there is a limit to the number of nodes that a single instance of Unified Manager can monitor before you need to install a second instance of Unified Manager. See the Best Practices Guide for more details.
Memory-page swapping negatively impacts the performance of the system and the management application. Competing for CPU resources that are unavailable because of overall host utilization can degrade performance.
Dedicated use requirement
The physical or virtual system on which you install Unified Manager must be used exclusively for Unified Manager and must not be shared with other applications. Other applications might consume system resources and can drastically reduce the performance of Unified Manager.
Space requirements for backups
If you plan to use the Unified Manager backup and restore feature, you must allocate additional capacity so that the “data” directory or disk has 150 GB of space. A backup can be written to a local destination or to a remote destination. The best practice is to identify a remote location that is external to the Unified Manager host system that has a minimum of 150 GB of space.
Host connectivity requirements
The physical system or virtual system on which you install Unified Manager must be configured in such a way that you can successfully ping the host name from the host itself. In case of IPv6 configuration, you should verify that ping6 to the host name is successful to ensure that the Unified Manager installation succeeds.
You can use the host name (or the host IP address) to access the product web UI. If you configured a static IP address for your network during deployment, then you designated a name for the network host. If you configured the network using DHCP, you should obtain the host name from the DNS.
If you plan to allow users to access Unified Manager by using the short name instead of using the fully qualified domain name (FQDN) or IP address, then your network configuration has to resolve this short name to a valid FQDN.
Mounted /opt/netapp or /opt/netapp/data requirements
You can mount /opt/netapp or /opt/netapp/data on an NAS or SAN device. Note that using remote mount points may cause scaling issues. If you do use a remote mount point, ensure that your SAN or NAS network has sufficient capacity to meet the I/O needs of Unified Manager. This capacity will vary and may increase based on the number of clusters and storage objects you are monitoring.
If you have mounted /opt/netapp or /opt/netapp/data from anywhere other that the root file system, and you have SELinux enabled in your environment, you must set the correct context for the mounted directories.
See the topic SELinux requirements for mounting /opt/netapp or /opt/netapp/data on an NFS or CIFS share for information about setting the correct SELinux context.