Please enter search query.
Search <book_title>...
Veritas Access Installation Guide
Last Published:
2018-07-27
Product(s):
Access (7.3.1)
Platform: Linux
- 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 6.8
- Required operating system RPMs for OL 7.3
- Required operating system RPMs for OL 7.4
- Required operating system RPMs for RHEL 6.6
- Required operating system RPMs for RHEL 6.7
- Required operating system RPMs for RHEL 6.8
- 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 NIC bonding and NIC exclusion
- 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. Troubleshooting the LTR upgrade
- Appendix C. Configuring the secure shell for communications
Configuring I/O fencing
Veritas Access supports two fencing modes: disk-based fencing for a cluster with shared disks, and majority-based fencing for a cluster with local DAS disks.
If you intend to use both shared disks (SAN) and local disks, majority-based fencing must be used. Veritas recommends that you do not configure I/O fencing through the installer.
- During the Veritas Access configuration, after the product is started, the installer asks whether to configure fencing:
Do you want to configure I/O Fencing in enabled mode? [y,n,q,?] (y)
- Enter y to configure fencing.
If the cluster does not include initialized shared disks, majority-based fencing mode is configured.
The I/O fencing would be configured in majority mode.
If shared disks are connected and initialized, disk-based I/O fencing is configured. You are prompted to choose disks.
Note:
You can choose three available VxVM disks or initialize three disks as VxVM disks to form the fencing disk group. You must choose exactly three disks.
- The installer stops the product, and applies the fencing configuration before restart.