Skip to main content
SnapCenter software

Requirements to install SnapCenter Server

PDFs

Before you install SnapCenter Server either on Windows or Linux host, you should review and ensure that all the requirements are met for your environment.

Domain and workgroup requirements for Windows host

The SnapCenter Server can be installed on a Windows host that is either in a domain or in a workgroup.

The user having admin privileges is allowed to install the SnapCenter server.

  • Active Directory domain: You must use a Domain user with local administrator rights. The Domain user must be a member of the local Administrator group on the Windows host.

  • Workgroups: You must use a local account that has local administrator rights.

While domain trusts, multi-domain forests, and cross-domain trusts are supported, cross-forest domains are not supported. The Microsoft documentation about Active Directory Domains and Trusts contains more information.

Note After installing the SnapCenter Server, you should not change the domain in which the SnapCenter host is located. If you remove the SnapCenter Server host from the domain it was in when the SnapCenter Server was installed and then try to uninstall SnapCenter Server, the uninstall operation fails.

Space and sizing requirements

You should be familiar with the space and sizing requirements.

Item Windows host requirements Linux host requirements

Operating Systems

Microsoft Windows

Only English, German, Japanese, and simplified Chinese version of the operating systems are supported.

For the latest information about supported versions, see NetApp Interoperability Matrix Tool.

  • Red Hat Enterprise Linux (RHEL) 8 and 9

  • SUSE Linux Enterprise Server (SLES) 15

For the latest information about supported versions, see NetApp Interoperability Matrix Tool.

Minimum CPU count

4 cores

4 cores

Minimum RAM

8 GB

Note The MySQL Server buffer pool uses 20 percent of the total RAM.

8 GB

Minimum hard drive space for the SnapCenter Server software and logs

7 GB

Note If you have the SnapCenter repository in the same drive where SnapCenter Server is installed, then it is recommended to have 15 GB.

15 GB

Minimum hard drive space for the SnapCenter repository

8 GB

Note NOTE: If you have the SnapCenter Server in the same drive where SnapCenter repository is installed, then it is recommended to have 15 GB.

Not applicable

Required software packages

  • ASP.NET Core Runtime 8.0.12 (and all subsequent 8.0.x patches) Hosting Bundle

  • PowerShell 7.4.2 or later

For .NET specific troubleshooting information, see SnapCenter upgrade or install fails for legacy systems that do not have internet connectivity.

  • .NET Framework 8.0.12 (and all subsequent 8.0.x patches)

  • PowerShell 7.4.2 or later

  • Nginx is a web server that can be used as a reverse proxy

  • Pam-devel

    PAM (Pluggable Authentication Modules) is a system security tool which allows system administrators to set authentication policy without having to recompile programs which do authentication.
Note ASP.NET core needs IIS_IUSRS to access the temp file system in SnapCenter Server on Windows.

SAN host requirements

SnapCenter does not include host utilities or a DSM. If the SnapCenter host is part of a SAN (FC/iSCSI) environment, you might need to install and configure additional software on the SnapCenter Server host.

  • Host Utilities: The Host Utilities support FC and iSCSI, and it enables you to use MPIO on your Windows Servers. Learn More.

  • Microsoft DSM for Windows MPIO: This software works with Windows MPIO drivers to manage multiple paths between NetApp and Windows host computers. A DSM is required for high availability configurations.

    Note If you were using ONTAP DSM, you should migrate to Microsoft DSM. For more information, see How to migrate from ONTAP DSM to Microsoft DSM.

Browser requirements

SnapCenter software supports Chrome 125 and later and Microsoft Edge 110.0.1587.17 and later.

Port requirements

The SnapCenter software requires different ports for communication between different components.

  • Applications cannot share a port.

  • For customizable ports, you can select a custom port during installation if you do not want to use the default port.

  • For fixed ports, you should accept the default port number.

  • Firewalls

    • Firewalls, proxies, or other network devices should not interfere with connections.

    • If you specify a custom port when you install SnapCenter, you should add a firewall rule on the plug-in host for that port for the SnapCenter Plug-in Loader.

The following table lists the different ports and their default values.

Port Name Port Numbers Protocol Direction Description

SnapCenter port

8146

HTTPS

Bidirectional

This port is used for communication between the SnapCenter client (the SnapCenter user) and the SnapCenter Server and is also used for communication from the plug-in hosts to the SnapCenter Server.

You can customize the port number.

SnapCenter SMCore communication port

8145

HTTPS

Bidirectional

This port is used for communication between the SnapCenter Server and the hosts where the SnapCenter plug-ins are installed.

You can customize the port number.

Scheduler Service Port

8154

HTTPS

This is port is used to orchestrate the SnapCenter scheduler workflows for all the managed plug-ins within the SnapCenter server host in centralized manner.

You can customize the port number.

RabbitMQ Port

5672

TCP

This is the default port that RabbitMQ listens on and it is used for publisher-subscriber model communication between Scheduler service and SnapCenter.

MySQL port

3306

HTTPS

The port is used for communicating with SnapCenter repository database. You can create secured connections from the SnapCenter Server to the MySQL server. Learn more

Windows plug-in hosts

135, 445

TCP

This port is used for communication between the SnapCenter Server and the host on which the plug-in is being installed. Additional dynamic port range specified by Microsoft should also be open.

Linux or AIX plug-in hosts

22

SSH

Unidirectional

This port is used for communication between the SnapCenter Server and the host, initiated from the server to client host.

SnapCenter Plug-ins Package for Windows, Linux or AIX

8145

HTTPS

Bidirectional

This port is used for communication between SMCore and hosts where the plug-ins package is installed. Customizable.

You can customize the port number.

SnapCenter Plug-in for Oracle Database

27216

The default JDBC port is used by the plug-in for Oracle for connecting to the Oracle database.

SnapCenter Plug-in for Exchange Database

909

The default NET.TCP port is used by the plug-in for Windows for connecting to the Exchange VSS call-backs.

NetApp supported plug-ins for SnapCenter

9090

HTTPS

This is an internal port that is used only on the plug-in host; no firewall exception is required.

Communication between the SnapCenter Server and plug-ins is routed through port 8145.

ONTAP cluster or SVM communication port

  • 443 (HTTPS)

  • 80 (HTTP)

  • HTTPS

  • HTTP

Bidirectional

The port is used by the SAL (Storage Abstraction Layer) for communication between the host running SnapCenter Server and SVM. The port is currently also used by the SAL on SnapCenter for Windows Plug-in hosts for communication between the SnapCenter plug-in host and SVM.

SnapCenter Plug-in for SAP HANA Database

  • 3instance_number13

  • 3instance_number15

  • HTTPS

  • HTTP

Bidirectional

For a multitenant database container (MDC) single tenant, the port number ends with 13; for non MDC, the port number ends with 15.

You can customize the port number.

SnapCenter Plug-in for PostgreSQL

5432

This port is the default PostgreSQL port used for communication by the plug-in for PostgreSQL to the PostgreSQL cluster.

You can customize the port number.