Veritas Access Installation Guide
- Introducing Veritas Access
- Licensing in Veritas Access
- System requirements
- Important release information
- System requirements
- Linux requirements
- Operating system RPM installation requirements and operating system patching
- Kernel RPMs that are required to be installed with exact predefined RPM versions
- OL kernel RPMs that are required to be installed with exact predefined RPM versions
- Required operating system RPMs for OL 7.4
- Required operating system RPMs for RHEL 7.3
- Required operating system RPMs for RHEL 7.4
- Software requirements for installing Veritas Access in a VMware ESXi environment
- Hardware requirements for installing Veritas Access virtual machines
- Management Server Web browser support
- Supported NetBackup versions
- Supported OpenStack versions
- Supported Oracle versions and host operating systems
- Supported IP version 6 Internet standard protocol
- Linux requirements
- Network and firewall requirements
- Maximum configuration limits
- Preparing to install Veritas Access
- Deploying virtual machines in VMware ESXi for Veritas Access installation
- Installing and configuring a cluster
- Installation overview
- Summary of the installation steps
- Before you install
- 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
- Replacing an Ethernet interface card
- Configuring I/O fencing
- About configuring Veritas NetBackup
- About enabling kdump during an Veritas Access configuration
- Reconfiguring the Veritas Access cluster name and network
- Configuring a KMS server on the Veritas Access cluster
- Automating Veritas Access installation and configuration using response files
- Displaying and adding nodes to a cluster
- Upgrading Veritas Access and operating system
- Upgrading Veritas Access using 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
OpenDedup ports and disabling the iptable rules
This use case is specific to running OpenDedup on Veritas Access. Each time a SDFS volume is created and mounted on Veritas Access, it starts listening on a specific port. Initially, it starts with port 6442 and goes on incrementing +1 for further subsequent volumes.
Table: OpenDedup ports
Port Range | Protocol or Service | Purpose | Impact if Blocked |
|---|---|---|---|
Starts from 6442 and increments +1 for subsequent volumes | TCP | Allows communication between Veritas Access and OpenDedup | Veritas Access cannot communicate with OpenDedup |
To allow communication to the OpenDedup port running on Veritas Access, disable the iptable rules completely
- Use the df command to show that the SDFS volume is mounted and on which port it is listening.
The SDFS volume is already mounted as part of the LTR script.
[root@ltrclust_02 ~]# df -h | tail -2 sdfs:/etc/sdfs/pool100-volume-cfg.xml:6442 11G 0 11G 0% /pool100
- Use the netstat command to verify that the port is open.
[root@ltrclust_02 ~]# netstat -tulpn | grep 6442 tcp 0 0 :::6442 :::* LISTEN 3761/jsvc.exec
- Disable the iptable rules to allow communication to the OpenDedup port once the volume is mounted and to disallow traffic to this port once the volume is unmounted.
Use the following commands to disable the iptable rules:
[root@ltrclust_02 ~]# iptables -F
[root@ltrclust_02 ~]# /etc/init.d/iptables stop
[root@ltrclust_02 ~]# iptables -L
Use the iptables -L command to verify that all the iptable rules are disabled.
The iptable rules should be run on all the Veritas Access cluster nodes and on the NetBackup media server if OpenDedup is installed on it.
- An alternative to disabling the iptable rules in Step 3 is to add an iptable rule to open the OpenDedup port, so that the existing iptable rules are also used.
Example:
[root@ltrclust_02 ~]# iptables -A INPUT -p tcp --dport 6442 -j ACCEPT