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
Displaying the nodes in the cluster
You can display all the nodes in the cluster, their states, CPU load, and network load during the past 15 minutes.
If you use the Cluster> show currentload option, you can display the CPU and network loads collected from now to the next five seconds.
To display a list of nodes in the cluster
- To display a list of nodes that are part of a cluster, and the systems that are available to add to the cluster, enter the following:
Cluster> show
Command output includes the following information. See examples below.
Node
Displays the node name if the node has already been added to the cluster. Displays the IP address of the node if it is still in the process of being added to the cluster.
Example:
node_01
or
192.168.30.10
State
Displays the state of the node or the installation state of the system along with an IP address of the system if it is installed.
See About the Veritas Access installation states and conditions.
CPU
Indicates the CPU load.
pubethX
Indicates the network load for the Public Interface X.
bondX
Indicates the network load for bond NIC X.
- For nodes already in the cluster, the following is displayed:
Node State CPU(15 min) pubeth0(15 min) pubeth1(15 min) % rx(MB/s) tx(MB/s) rx(MB/s) tx(MB/s) ------ ------- ----------- -------- -------- -------- -------- snas_01 RUNNING 1.35 0.00 0.00 0.00 0.00 snas_02 RUNNING 1.96 0.00 0.00 0.00 0.00 - For the nodes that are being added to the cluster, for the nodes that are being deleted from the cluster, and for the nodes that is getting upgraded, the following progress is displayed:
Nodes in Transition Node/IP Operation State Description ------ --------- ----- ----------- 192.168.30.11 Add node FAILED Installing packages snas_03 Delete node ONGOING Removing node snas_01,snas_02 Rolling upgrade ONGOING Rolling upgrade phase 2
Note:
The add node and delete node operations cannot be performed at the same time.
- To display the CPU and network loads collected from now to the next five seconds, enter the following:
Cluster> show currentload
Example output:
Node State CPU(5 sec) pubeth0(5 sec) pubeth1(5 sec) % rx(MB/s) tx(MB/s) rx(MB/s) tx(MB/s) ---- ----- ---------- -------- -------- -------- -------- snas_01 RUNNING 0.26 0.01 0.00 0.01 0.00 snas_02 RUNNING 0.87 0.01 0.00 0.01 0.00 snas_03 RUNNING 10.78 27.83 12.54 0.01 0.00Statistics for network interfaces are shown for each public interface available on the cluster nodes.