Please enter search query.
Search <book_title>...
Cluster Server 7.4.1 Configuration and Upgrade Guide - Linux
Last Published:
2019-06-18
Product(s):
InfoScale & Storage Foundation (7.4.1)
Platform: Linux
- Section I. Configuring Cluster Server using the script-based installer
- I/O fencing requirements
- Preparing to configure VCS clusters for data integrity
- About planning to configure I/O fencing
- Setting up the CP server
- Configuring VCS
- Configuring a secure cluster node by node
- Completing the VCS configuration
- Verifying and updating licenses on the system
- Configuring VCS clusters for data integrity
- Setting up disk-based I/O fencing using installer
- Setting up server-based I/O fencing using installer
- Section II. Automated configuration using response files
- Performing an automated VCS configuration
- Performing an automated I/O fencing configuration using response files
- Section III. Manual configuration
- Manually configuring VCS
- Configuring LLT manually
- Configuring VCS manually
- Configuring VCS in single node mode
- Modifying the VCS configuration
- Manually configuring the clusters for data integrity
- Setting up disk-based I/O fencing manually
- Setting up server-based I/O fencing manually
- Configuring server-based fencing on the VCS cluster manually
- Setting up non-SCSI-3 fencing in virtual environments manually
- Setting up majority-based I/O fencing manually
- Manually configuring VCS
- Section IV. Upgrading VCS
- Planning to upgrade VCS
- Performing a VCS upgrade using the installer
- Tasks to perform after upgrading to 2048 bit key and SHA256 signature certificates
- Performing an online upgrade
- Performing a phased upgrade of VCS
- About phased upgrade
- Performing a phased upgrade using the product installer
- Performing an automated VCS upgrade using response files
- Planning to upgrade VCS
- Section V. Adding and removing cluster nodes
- Adding a node to a single-node cluster
- Adding a node to a single-node cluster
- Adding a node to a multi-node VCS cluster
- Manually adding a node to a cluster
- Setting up the node to run in secure mode
- Configuring I/O fencing on the new node
- Adding a node using response files
- Removing a node from a VCS cluster
- Removing a node from a VCS cluster
- Removing a node from a VCS cluster
- Adding a node to a single-node cluster
- Section VI. Installation reference
- Appendix A. Services and ports
- Appendix B. Configuration files
- Appendix C. Configuring LLT over UDP
- Using the UDP layer for LLT
- Manually configuring LLT over UDP using IPv4
- Manually configuring LLT over UDP using IPv6
- Appendix D. Configuring LLT over TCP
- Manually configuring LLT over TCP using IPv4
- Manually configuring LLT over TCP using IPv6
- Appendix E. Migrating LLT links from IPv4 to IPv6 or dual-stack
- Appendix F. Using LLT over RDMA
- Configuring LLT over RDMA
- Configuring RDMA over an Ethernet network
- Configuring RDMA over an InfiniBand network
- Tuning system performance
- Manually configuring LLT over RDMA
- Troubleshooting LLT over RDMA
- Appendix G. Configuring the secure shell or the remote shell for communications
- Appendix H. Installation script options
- Appendix I. Troubleshooting VCS configuration
- Appendix J. Sample VCS cluster setup diagrams for CP server-based I/O fencing
- Appendix K. Upgrading the Steward process
Enabling rsh for Linux
The following section describes how to enable remote shell.
Veritas recommends configuring a secure shell environment for Veritas InfoScale product installations.
See Manually configuring passwordless ssh.
See the operating system documentation for more information on configuring remote shell.
To enable rsh for rhel6/sles
- To ensure that the rsh and rsh-server RPMs are installed, type the following command:
# rpm -qa | grep -i rsh
If it is not already in the file, type the following command to append the line "rsh" to the /etc/securetty file:
# echo "rsh" >> /etc/securetty
- Modify the line disable = no in the /etc/xinetd.d/rsh file.
- In the /etc/pam.d/rsh file, change the "auth" type from "required" to "sufficient":
auth sufficient
- Add the "promiscuous" flag into /etc/pam.d/rsh and /etc/pam.d/rlogin after item "pam_rhosts_auth.so".
- To enable the rsh server, type the following command:
# chkconfig rsh on
- Modify the .rhosts file. Each line of the .rhosts file contains a fully qualified domain name or IP address for each remote system. This file also contains the name of a user having access to the local system. For example, if the root user must remotely access sys1 from sys2, add an entry for sys2.companyname.com to the .rhosts file on sys1 by typing the following command:
# echo "sys2.companyname.com" >> $HOME/.rhosts
- Install the Veritas InfoScale product.
To disable rsh for rhel6/sles
- Remove the "rsh" entry in the /etc/securetty file.
- Disable the rsh server by typing the following command:
# chkconfig rsh off
- After you complete an installation procedure, delete the .rhosts file from each user's $HOME directory to ensure security:
# rm -f $HOME/.rhosts
To enable rsh for rhel7
- Run the following commands to enable rsh passwordless connection:
# systemctl start rsh.socket # systemctl start rlogin.socket # systemctl enable rsh.socket # systemctl enable rlogin.socket # echo rsh >> /etc/securetty # echo rlogin >> /etc/securetty #echo "+ +" >> /root/.rhosts
To disable rsh for rhel7
- Run the following commands to disable rsh passwordless connection:
# systemctl stop rsh.socket # systemctl stop rlogin.socket # systemctl disable rsh.socket # systemctl disable rlogin.socket