Search <book_title>...

Veritas Access Installation Guide

Last Published: 2019-09-30

Product(s): Access (7.4.2)

Platform: Linux

Licensing in Veritas Access
System requirements
Preparing to install Veritas Access
Deploying virtual machines in VMware ESXi for Veritas Access installation
Installing and configuring a cluster
Automating Veritas Access installation and configuration using response files
Displaying and adding nodes to a cluster
Upgrading the operating system and Veritas Access
1. Supported upgrade paths for upgrades on RHEL
2. Upgrading the operating system and Veritas Access
Performing a rolling upgrade
1. About rolling upgrade
2. Performing a rolling upgrade using the installer
Uninstalling Veritas Access
1. Before you uninstall Veritas Access
2. Uninstalling Veritas Access using the installer
  1. Removing Veritas Access 7.4.2 RPMs
  2. Running uninstall from the Veritas Access 7.4.2 disc
Appendix A. Installation reference
1. Installation script options
Appendix B. Configuring the secure shell for communications
1. Manually configuring passwordless secure shell (ssh)
2. Setting up ssh and rsh connections using the pwdutil.pl utility
Appendix C. Manual deployment of Veritas Access
1. Deploying Veritas Access manually on a two-node cluster in a non-SSH environment
2. Enabling internal sudo user communication in Veritas Access

Enabling internal sudo user communication in Veritas Access

By default, Veritas Access uses SSH communication between the nodes for the root user. If you want to use sudo user-based communication, you can set the internal communication to use the sudo user communication after you have installed Veritas Access successfully.

You can use the following steps to set up the sudo user communication.

Phase 1: Create an access_user on each of the nodes of the Veritas Access cluster

Create the access_user and set the password.

For example:

[root@access1_01 ~]# useradd access_user
[root@access1_01 ~]# passwd access_user
Changing password for user access_user.
New password:
Retype new password:
passwd: all authentication tokens updated successfully.

Add the access_user to the sudoers file.
For example:
```
[root@access1_01 ~]# echo "access_user ALL=(ALL) NOPASSWD: ALL" 
>> /etc/sudoers
```
Complete Phase 1 on all the nodes of the cluster.

Phase 2: Set up a passwordless communication between the root and access_user on each node

Generate rsa key for the root user if it is not present.

For example:

[root@access1_01 ~]# ssh-keygen
Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_rsa):
Created directory '/root/.ssh'.
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /root/.ssh/id_rsa.
Your public key has been saved in /root/.ssh/id_rsa.pub.
The key fingerprint is:
SHA256:hRIBljcpsmGMCtfUUjyVGOfe957OXyiXcRyiYBprmZk root@access1_01
The key's randomart image is:
+---[RSA 2048]----+
| o o+*=*o.       |
|o *.= O+..       |
|oo + +.+oo.  . . |
|. .    oXo. . ...|
|       ES ... . o|
|      .    . . = |
|            . = .|
|             = ..|
|             .=..|
+----[SHA256]-----+

Copy the rsakey.pub of the root user to the access_user for each of the nodes in the cluster.

For example:

[root@access1_01 ~]# ssh-copy-id access_user@access1_01
/usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed:
"/root/.ssh/id_rsa.pub"
/usr/bin/ssh-copy-id: INFO: attempting to log in with the new 
key(s),to filter out any that are already installed
/usr/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- 
if you are prompted now it is to install the new keys
access_user@access1_01's password:

Number of key(s) added: 1

Phase 3: Select the communication type as SUDO_SSH

Create the /opt/VRTSnas/conf/communication.conf file.

[root@access1_01 ~]# cat /opt/VRTSnas/conf/communication.conf
{
    "WorkingVersion": "1",
    "Version": "1",
    "CommunicationType": "SUDO_SSH"
}