Veritas Access Installation Guide
- Introducing Veritas Access
- Licensing in Veritas Access
- System requirements
- System requirements
- Linux 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 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
Before you install
Before you install the Veritas Access software:
Make sure that the names of all the public and private interface which are targeted to be part of access configuration during installation should be same across all the Veritas Access cluster nodes on which you want to install Veritas Access.
If the system has a network interface bond before you install Veritas Access, you need to specify the bond names as bond0, bond1, bond2 and so on, and then you can start the Veritas Access installation.
Before you install Veritas Access, if the system has VLAN configured network interface on it and if the user want to configure it on the Veritas Access nodes, then the interface name on which VLAN is configured must follow the naming format as follows:
interface_name.vlan_id
For example, eth0.100 or ens168.101.
Make sure that no DHCP servers are running in the private network.
Disable the USB Ethernet interface in BIOS for all the nodes in the cluster.
Make sure that there are at least two private connections between the cluster and the public connection. The public connected interface must be reachable to the gateway.
Connect DAS or SAN storage to the cluster node. If you are configuring the fencing feature to avoid the split-brain condition, make sure that the SAN disks are SCSI3-compliant.
Assign one public IP address to each node in a cluster. This IP address is used by the installer, and it is reused as one of the public interface physical IP addresses after configuration.
Make sure that the assigned IP is persistent after a reboot. To make the IP persistent, do the following changes in
/etc/sysconfig/network-scripts/ifcfg-XX
For example:
TYPE=Ethernet HWADDR=00:50:56:3d:f1:3e DEVICE=eth2 BOOTPROTO=none IPADDR=10.200.56.214 NETMASK=255.255.252.0 NM_CONTROLLED=no ONBOOT=yes
Note:
Make sure that you have enough public IPs required to install the Veritas Access software.