Required Networking Ports for Qumulo Core

DETAILS

Qumulo Core listens on the following ports for inbound connections:

Port	Protocols	Use
21	TCP	FTP
22	TCP	SSH
80	TCP	HTTP (Web UI)
111	TCP, UDP	`rpcbind`or `portmapper` for NFSv3
443	TCP	HTTPS (Web UI)
445	TCP	SMB
2049	TCP, UDP	NFS/MOUNT NOTE: UDP is supported for the MOUNT protocol for older clients that require it, but will not be used at all for any NFS clients specifying the TCP mount option or for transferring data over NFS after mounting.
3712	TCP	Replication
8000	TCP	REST API
32768-60999	TCP	FTP Passive Mode

Qumulo Core uses the following ports for outbound connections:

Port	Protocols	Use
53	UDP	DNS
88	TCP	Kerberos
111	TCP	`rpcbind` or `portmapper` for NSM and NLM NOTE: Depending on the client`portmapper`configuration, additional ports might be required.
123	UDP	Synchronizing product and network time (for authentication and timestamps of artifacts such as audit logs) using the Network Time Protocol (NTP)
135	TCP	DCERPC/Netlogon (Domain Controller Binding)
389	TCP	LDAP to AD or standalone LDAP server*
443	TCP	Qumulo Shift for Amazon S3*
514	TCP	Audit using `Rsyslog`*
3712	TCP	Replication*

Notes:

Items marked with * are default uses. You can reconfigure these ports.
For cluster formation and inter-node communication Qumulo Core requires the following:
- Hardware Platforms: Unblocked IPv6 traffic in the local subnet. For more information, see Configuring IPv6 in Qumulo Core.
- Cloud Platforms: Unblocked IPv4 traffic in the local subnet

You should now be able to successfully configure the networking ports required for Qumulo Core.

NOTE: Active Directory authentication services require their own network port range. For an authoritative list, see Active Directory and Active Directory Domain Service Port Requirements.

Like what you see? Share this article with your network!

Was this article helpful?

0 out of 0 found this helpful

0 comments

Please sign in to leave a comment.