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
Reconfiguring the Veritas Access cluster name and network
After you install and configure Veritas Access, you can reconfigure the cluster name and network, if required.
Before you reconfigure the cluster, you have to enable the support user for the nodes because the root user access authority is forbidden. The support user default password is veritas. You can change the password after you log on the first time.
To reconfigure the Veritas Access cluster name and network
- Log on to the host console using the support user name and password.
- Ensure that all the service groups are offline. Enter the following command:
/opt/VRTS/install/installaccess -updateparameter
- Enter the private IPs of the systems.
172.16.0.3 172.16.0.4
Note:
Only the private IPs of the systems must be entered. Public IPs should not be used here.
- Enter the cluster name and network information.
Enter the cluster name: Enter the public IP starting address: Enter the netmask for the public IP address: Enter the number of VIPs per interface: Enter the virtual IP starting address: Enter the default gateway IP address: Enter the DNS IP address: Enter the DNS domain name: Enter the console virtual IP address: Do you want to use the separate console port? [y,n,q] (n): Do you want to configure the Network Time Protocol(NTP) server to synchronize the system clocks? [y,n,q] (n) y: Enter the Network Time Protocol server:
The installer confirms that the information that you entered is correct. The configuration is completed and the new cluster and IPs are configured on the cluster.
The installer displays the location of the log and summary files. If required, view the files to confirm the configuration status.
Note:
The cluster name can contain only alpha characters, numbers, or underscores. The cluster name must start with a letter of the alphabet and can have a length of maximum 15 characters. Also, if a separate console port is chosen, the first public NIC is chosen to work exclusively as a console port.
Note:
If your cluster has DAS disks, limit the cluster name to 10 characters.
After formatting the DAS disks, do not change the cluster name.