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
About the Veritas Access installation states and conditions
Table: Veritas Access installation states describes the Veritas Access installation states.
Table: Veritas Access installation states
Installation state | Description |
|---|---|
RUNNING | Node is part of the cluster and the Veritas Access processes are running on it. |
FAULTED | Node is down and/or the Veritas Access processes are not running on it. |
LEAVING | Node is leaving the cluster gracefully |
EXITED | Node has exited the cluster gracefully |
UNKNOWN | Exact state of the node cannot be determined |
Depending on the cluster condition as described in Table: Cluster conditions and states, output for the Cluster> show command changes.
Table: Cluster conditions and states
Condition | Description |
|---|---|
If the node is configured and part of the cluster, but the node is powered off. | State displays as FAULTED, and there is no installation state or network statistics. |
If the node is configured and part of the cluster, but the node is physically removed from the cluster. | State displays as FAULTED, and there is no installation state or network statistics. |
If the node is configured and part of the cluster, but the node is shutdown using the Cluster> shutdown command. | State changes from LEAVING to EXITED. |
If the node is configured and part of the cluster, and you use the Cluster> del command. | Node is deleted from the cluster, and information about the deleted node is no longer available. |