Skip to main content
SnapCenter Software 6.0

Connection and port requirements

Contributors netapp-nsriram netapp-soumikd netapp-asubhas
PDFs

You should ensure that the connections and ports requirements are met before installing the SnapCenter Server and application or database plug-ins.

  • Applications cannot share a port.

    Each port must be dedicated to the appropriate application.

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

    You can change a plug-in port after installation by using the Modify Host wizard.

  • 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.

Type of port Default port

SnapCenter port

8146 (HTTPS), bidirectional, customizable, as in the URL https://server:8146

Used for communication between the SnapCenter client (the SnapCenter user) and the SnapCenter Server. Also used for communication from the plug-in hosts to the SnapCenter Server.

To customize the port, see Install the SnapCenter Server using the install wizard.

SnapCenter SMCore communication port

8145 (HTTPS), bidirectional, customizable

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

To customize the port, see Install the SnapCenter Server using the install wizard.

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.

To customize the port, see Install the SnapCenter Server using the install wizard.

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), bidirectional, customizable

The port is used for communication between SnapCenter and MySQL repository database.

You can create secured connections from the SnapCenter Server to the MySQL server. Learn more

To customize the port, see Install the SnapCenter Server using the install wizard.

Windows plug-in hosts

135, 445 (TCP)

In addition to ports 135 and 445, the dynamic port range specified by Microsoft should also be open. Remote install operations use the Windows Management Instrumentation (WMI) service, which dynamically searches this port range.

For information on the dynamic port range supported, see Service overview and network port requirements for Windows

The ports are used for communication between the SnapCenter Server and the host on which the plug-in is being installed. To push plug-in package binaries to Windows plug-in hosts, the ports must be open only on the plug-in host, and they can be closed after installation.

Linux or AIX plug-in hosts

22 (SSH)

The ports are used for communication between the SnapCenter Server and the host where the plug-in is being installed. The ports are used by SnapCenter to copy plug-in package binaries to Linux or AIX plug-in hosts and should be open or excluded from the firewall or iptables.

SnapCenter Plug-ins Package for Windows, SnapCenter Plug-ins Package for Linux or SnapCenter Plug-ins Package for AIX

8145 (HTTPS), bidirectional, customizable

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

The communication path also needs to be open between the SVM management LIF and the SnapCenter Server.

To customize the port, see Add hosts and install SnapCenter Plug-in for Microsoft Windows or Add hosts and install SnapCenter Plug-ins package for Linux or AIX.

SnapCenter Plug-in for Oracle Database

27216, customizable

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

To customize the port, see Add hosts and install SnapCenter Plug-ins package for Linux or AIX.

SnapCenter Plug-in for Exchange Database

909, customizable

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

To customize the port, see Add hosts and install Plug-in for Exchange.

NetApp supported plug-ins for SnapCenter

9090 (HTTPS), fixed

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

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

ONTAP cluster or SVM communication port

443 (HTTPS), bidirectional80 (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 vCode Spell Checkerports

3instance_number13 or 3instance_number15, HTTP or HTTPS, bidirectional, and customizable

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

For example, 32013 is the port number for instance 20 and 31015 is the port number for instance 10.

To customize the port, see Add hosts and install plug-in packages on remote hosts.

Domain controller communication port

See the Microsoft documentation to identify the ports that should be opened in the firewall on a domain controller for authentication to work properly.

It is necessary to open the Microsoft required ports on the domain controller so that the SnapCenter Server, Plug-in hosts, or other Windows client can authenticate the users.

To modify the port details, see Modify plug-in hosts.