CloudFS Administration Guide
      Back to home
      1. Knowledge Base
      2. Panzura CloudFS
      3. CloudFS Administration Guide

      Required Ports

      The following table lists the protocol ports that Panzura Filers use for operation.

      For each protocol port, the table lists the filer's physical port (LAN or WAN) that receives and sends traffic and whether sessions are initiated by the filer or by another device.

      • In: Session traffic is initiated by another device and received by the filer on the indicated port.
      • Out: Session traffic is initiated by the filer and sent out of the indicated port.
      • Both: Session traffic might be initiated locally or remotely.

      In the One-Arm column, LAN/WAN refers to both LAN and WAN traffic. When you connect a filer in One-Arm mode, use the LAN port on the filer for the physical connection to the network and leave the WAN port unconnected. In Inline mode, both the LAN and WAN ports are used.

      Port/Protocol Inline One-Arm Description
      LAN WAN LAN
      22/TCP Both   Both SSH (used for management traffic between filers)
      80/TCP
      443/TCP      		 In   In WebUI

      22/TCP

      80/TCP 

      443/TCP

      		   Out Out

      Support Assistance (SA)

      SA access can use any of these ports and requires at least 1 of them.

      Note: Support Assistance is optional but recommended. To use Support Assistance, the following also is required:

      • A route from the filer to the Internet.
      • Access to DNS. SA is located at the following URLs: 

        • saconnect.panzura.com

          support1.panzura.com

        • support2.panzura.com

        • support3.panzura.com

        • support4.panzura.com

        • support26.panzura.com

      Diagnostic logs may be automatically uploaded to SA using the following URL:

      • sadownload.panzura.com
      443/TCP   Out Out

      Licensing Panzura uses token licenses which decrypt to a central license server using the following URL:

      • support2.pixel8networks.com

      53/TCP

      53/UDP

      		 Both   Both DNS

      80/TCP

      443/TCP

      		   Out Out HTTP/HTTPS access to object store in cloud

      111/TCP

      111/UDP

      2049/TCP

      2049/UDP

      4045/TCP

      4045/UDP

      		 In   In

      Network File System (NFS) protocols: RPC, NFS, and lockd

      Note: Required only if NFS support will be enabled on the filer(s).
      123/UDP Out   Out Network Time Protocol (NTP)

      137/UDP

      138/UDP

      139/UDP

      		 Out   Out NetBIOS (WINS)

      161/TCP

      161/UDP

      162/TCP

      162/UDP

      		 Both   Both

      SNMP

      SNMP traps

      389/TCP

      389/UDP

      		 Both   Both

      LDAP

      Active Directory (AD)

      445/TCP

      445/UDP

      		 In   In SMB file protocol

      514/TCP

      514/UDP

      		 Out   Out

      Syslog

      Note: Optional. Needed only if the filer will send its logs to a remote syslog server.
      35357/TCP   Out Out

      HP Cloud object store

      Note: Required only if HP Cloud object store is used.
      ICMP In   In Ping replies

      892/TCP

      892/UDP

      		 In   In NFS server
      67/DHCP   Out Out DHCP/Bootstrap Protocol Server

      662/TCP

      662/UDP

      		 Both   Both PFTP

      42/TCP

      42/UDP

      		       Name Server, ARPA Host Name Server Protocol

      88/TCP

      88/UDP

      		 Out   Out

      Kerberos.

      Required for SMB operation. Optional for NFSv4, configured under NFS settings