Veritas Access Installation Guide
- Licensing in Veritas Access
- System requirements
- System requirements
- Linux requirements
- Network and firewall requirements
- Preparing to install Veritas Access
- Deploying virtual machines in VMware ESXi for Veritas Access installation
- Installing and configuring a cluster
- Installing the operating system on each node of the cluster
- Installing Veritas Access on the target cluster nodes
- About managing the NICs, bonds, and VLAN devices
- About VLAN tagging
- Automating Veritas Access installation and configuration using response files
- Displaying and adding nodes to a cluster
- Upgrading the operating system and Veritas Access
- Performing a rolling upgrade
- Uninstalling Veritas Access
- Appendix A. Installation reference
- Appendix B. Configuring the secure shell for communications
- Appendix C. Manual deployment of Veritas Access
Network and firewall requirements
Table: Default Veritas Access ports displays the default ports that Veritas Access uses to transfer information.
Table: Default Veritas Access ports
Port | Protocol or Service | Purpose | Impact if blocked |
---|---|---|---|
21 | FTP | Port where the FTP server listens for connections. Note: Users can configure another port if desired. | FTP features are blocked. |
22 | SSH | Secure access to the Veritas Access server | Veritas Access is not accessible. |
25 | SMTP | Sending SMTP messages. | The SMTP messages that are sent from Veritas Access are blocked. |
53 | DNS queries | Communication with the DNS server | Domain name mapping fails. |
111 | rpcbind | RPC portmapper services | RPC services fail. |
123 | NTP | Communication with the NTP server | Server clocks are not synchronized across the cluster. NTP-reliant features (such as DAR) are not available. |
139 | CIFS | CIFS client to server communication | CIFS clients cannot access the Veritas Access cluster |
161 | SNMP | Sending SNMP alerts | SNMP alerts cannot be broadcast. |
445 | CIFS | CIFS client to server communication | CIFS clients cannot access the Veritas Access cluster. |
514 | syslog | Logging program messages | Syslog messages are not recorded. |
756, 757, 755 | statd | NFS statd port | NFS v3 protocol cannot function correctly. |
2049 | NFS | NFS client to server communication | NFS clients cannot access the Veritas Access cluster. |
3172, 3173 | ServerView | ServerView port | ServerView cannot work. |
3260 | iSCSI | iSCSI target and initiator communication | Initiator cannot communicate with the target. |
4001 | mountd | NFS mount protocol | NFS clients cannot mount file systems in the Veritas Access cluster. |
4045 | lockd | Processes the lock requests | File locking services are not available. |
5634 | HTTPS | Management Server connectivity | Web GUI may not be accessible. |
56987 | Replication | File synchronization, Veritas Access replication | Veritas Access replication daemon is blocked. Replication cannot work. |
8088 | REST server | REST client to server communication | REST client cannot access REST API of Veritas Access. |
8143 | S3 | Data port for Veritas Access S3 server | User will not able to use Veritas Access object server. |
8144 | ObjectAccess service | Administration port for Veritas Access S3 server. | User cannot create access or secret keys for using Objectaccess service. |
10082 | spoold | Veritas Data Deduplication engine | Cannot use the Veritas Data Deduplication service for deduplicating data |
10102 | spad | Veritas Data Deduplication manager | Cannot use the Veritas Data Deduplication service for deduplicating data |
11211 | Memcached port | Veritas Access command-line interface framework | Veritas Access command-line interface cannot function correctly, and cluster configuration may get corrupted. |
30000:40000 | FTP | FTP passive port | FTP passive mode fails. |
14161 | HTTPS | Veritas Access GUI | User is unable to access Veritas Access GUI |
51001 | UDP | LLT over RDMA | LLT is not working. |
51002 | UDP | LLT over RDMA | LLT is not working. |