Connection and port requirements for SnapCenter installation

Connections and ports must meet minimum requirements before you can install SnapCenter.

Applications cannot share a port.
All ports 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 port number after installation by using the Modify Host wizard.
For fixed ports, you must 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 must add a firewall rule on the plug-in host for that port for the SnapCenter Plug-in Loader.
  Note: This rule does not apply to the SnapCenter Plug-in for VMware vSphere. A firewall rule is added on SnapCenter Plug-in for VMware vSphere hosts when the plug-in is installed.

SnapCenter uses the following default ports:

Type of port	Default port
SnapCenter port	8146 (HTTPS), bidirectional, fixed, 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.
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.
MySQL port	3306 (HTTPS), bidirectional 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. Details are in the Administration Guide. Performing administrative tasks
Windows plug-in hosts	135, 445 (TCP) In addition to ports 135 and 445, ports 49152 through 65535 should also be open. Remote install operations use the Windows Management Instrumentation (WMI) service, which dynamically searches this port range. SnapCenter also searches ports 49152 through 65535 in Windows Server 2008 and later (1024 through 1034 in Windows Server 2003 and earlier) for open ports. The ports are used for communication between the SnapCenter Server and the host where 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 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 plug-in hosts and should be open or excluded from the firewall or iptables.
SnapCenter Plug-ins Package for Windows	8145 (HTTPS), bidirectional, customizable The port is used for communication between SMCore and hosts where the SnapCenter plug-ins are installed. The communication path needs to be open between the SVM management LIF and the SnapCenter Server.
SnapCenter Plug-ins Package for Linux	8145 (HTTPS), bidirectional, customizable The port is used for communication between SMCore and hosts where the SnapCenter plug-ins are installed. The communication path needs to be open between the SVM management LIF and the SnapCenter Server.
Custom 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.
VMware vSphere vCenter Server port	443 (HTTPS), unidirectional The port is used for communication between the SnapCenter Plug-in for VMware vSphere and vCenter server. The port is also used by all SnapCenter plug-ins for Windows hosts to connect to the vCenter Server.
SnapCenter Plug-in for VMware vSphere port	8144 (HTTPS), bidirectional, customizable Used for communications from the vCenter vSphere web client and from the SnapCenter Server. Note: You cannot modify the port if the plug-in is installed on the SnapCenter Server host. Important: If you use a port different from 8144, ensure that the port appears in the firewall exception list.
SnapCenter Server and SVM communication port	443 (HTTPS), bidirectional 80 (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 ports	3`instance_number`13 or 3`instance_number`15, 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.