IN THIS ARTICLE
Outlines the networking ports required for Qumulo Core
- Cluster running Qumulo Core
Qumulo Core listens on the following ports for inbound connections:
|80||TCP||HTTP (Web UI)|
|111||TCP, UDP||rpcbind/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:
rpcbind/portmapper for NSM and NLM.
NOTE: additional ports will be required based on client portmapper configuration for NSM and NLM.
|389||TCP||LDAP to AD or Standalone LDAP server*|
|443||TCP||Qumulo Shift for Amazon S3*|
|514||TCP||Audit via rsyslog*|
|*By default. Actual port is configurable.|
Qumulo Core requires unblocked IPv6 traffic in the local subnet for cluster formation and for inter-node communication since a single, ephemeral port will be allocated at any given time. Reference the Configuring IPv6 in Qumulo Core article for additional details.
You should now be able to successfully configure the networking ports required for Qumulo Core
NOTE: Active Directory authentication services will require their own range of network ports. Please refer to the article linked above for an authoritative list.
Like what you see? Share this article with your network!