Port Configuration

This topic provides information about the ports used by various components and processes.

In general, you can configure the protocols below as follows to secure your environment.

  • HTTP, HTTPS: Enabled; Quantum recommends you review the following sections for proper configuration.
  • SSH: Enabled; Quantum recommends you review the following sections for proper configuration.
  • Telnet: Disabled

In order for StorNext, StorNext Connect, the StorNext Unified UI, license reporting, software updates, and CBA to fully function, the following host names should be added to the firewall rules for your network for https port 443:

  • stornextconnect.quantum.com

  • api-stornextconnect.quantum.com

  • mystornext.quantum.com

  • api-mystornext.quantum.com

  • insight.quantum.com

  • api-as.quantum.com

The following table lists ports that are used by StorNext and its ancillary components.

Port

Protocol

StorNext Use

Notes

81

TCP

GUI (Java),
Web Services

User starts at port 81, redirected to 443

443

TCP

GUI (Java),
Web Services

 

1062, 1063

TCP

Blockpool

Both ports if HA primary

1527

TCP

GUI (Java connection to derby db)

 

3307

TCP

GUI (Java connection to MySQL)

 

5164

TCP

fsmpm

 This is the TCP port for the StorNext file system alternate portmapper. See the fsports(4) man page for information on changing the default setting.

5189

TCP

HA Manager

 

14500

TCP

snpolicyd

 
14510, 14511 TCP DDM  

20566

TCP

MySQL

Only used internally on an MDC.

60001, 60002 …

TCP

ACSLS Tape Libraries

Not used by StorNext, but related

Various

TCP

fsm, fsmpm

These ports are used to for metadata exchanges between client hosts and FSM processes on the MDCs and for additional exchanges between StorNext components on hosts within the cluster. See the fsports(4) man page for information on setting up a range of ports that will be used.

Various

UDP

fsmpm

These ports are used to exchange heartbeat messages between the client hosts and the coordinator hosts. See the fsports(4) man page for information on setting up a range of ports that will be used.

The following table lists ports that are used by the Quantum Unified User Interface (new UI introduced in StorNext 7.0.1) and its ancillary components.

Port

Protocol

Use
22

SSH

Connection from a Quantum appliance to a StorNext client.
80

HTTP

Connection from the Connector on a Quantum appliance or on a StorNext client to a Quantum appliance.
442

HTTPS

Connection from a browser to Quantum appliance.
443

HTTPS

Connection from a browser to Quantum appliance running StorNext software GUI.
2004

TCP

Connection from a StorNext client to a Quantum appliance.
5163

TCP

Connection from a Quantum appliance running StorNext to the Connector on a StorNext client.
8443, 8445

HTTPS

Connection from a browser to the Quantum Unified User Interface (new UI introduced in StorNext 7.0.1).

The following table lists ports that are used by Cloud Based Analytics and its ancillary components.

Port

Protocol

Use
443

HTTPS

Connection to the portal.

FlexTier allows you to tier to multiple Object Store locations, both public and private; each can have different ports and configuration options. See your provider for information about which ports you can configure for use with FlexTier.

The following table lists ports that are used by Appliance Controller and its ancillary components.

Port

Protocol

Use
111 TCP Used for rpcbind (for NFS).
112 Raw Used for keepalived.
445 TCP Used by the SMB server, if you have configured Samba.
2049 TCP Used for nfsd (for NFS).
10001 TCP Used for haproxy.
20048 TCP Used for rpc.mountd (for NFS).
33777

TCP

Used by the Appliance Controller.