IN THIS ARTICLE
This page outlines the networking ports required for Qumulo Core.
- A cluster running Qumulo Core
Qumulo Core listens on the following ports for inbound connections:
|80||TCP||HTTP (Web UI)|
|111||TCP, UDP||rpcbind or portmapper for NFS|
|443||TCP||HTTPS (Web UI)|
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.
|32768-60999||TCP||FTP Passive Mode|
Qumulo Core uses the following ports for outbound connections:
NOTE: Depending on client
|123||UDP||Synchronizing product and network time (for authentication and timestamps of artifacts such as audit logs) using the Network Time Protocol (NTP)|
|389||TCP||LDAP to AD or standalone LDAP server*|
|443||TCP||Qumulo Shift for Amazon S3*|
|514||TCP||Audit using Rsyslog*|
NOTE: Items marked with * are default uses. You can reconfigure these ports.
Because a single, ephemeral port is allocated at any given time, Qumulo Core requires unblocked IPv6 traffic in the local subnet for cluster formation and inter-node communication. For more information, see Configuring IPv6 in Qumulo Core.
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!