Connection and port requirements
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.
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 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 |
|
|
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 |
|
|
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. |
To modify the port details, see Modify plug-in hosts.