Please enter search query.
Search <book_title>...
Storage Foundation and High Availability 7.4 Configuration and Upgrade Guide - Linux
Last Published:
2019-02-11
Product(s):
InfoScale & Storage Foundation (7.4)
Platform: Linux
- Section I. Introduction to SFHA
- Section II. Configuration of SFHA
- Preparing to configure
- Preparing to configure SFHA clusters for data integrity
- About planning to configure I/O fencing
- Setting up the CP server
- Configuring the CP server manually
- Configuring CP server using response files
- Configuring SFHA
- Configuring Storage Foundation High Availability using the installer
- Configuring a secure cluster node by node
- Completing the SFHA configuration
- Verifying and updating licenses on the system
- Configuring Storage Foundation High Availability using the installer
- Configuring SFHA clusters for data integrity
- Setting up disk-based I/O fencing using installer
- Setting up server-based I/O fencing using installer
- Manually configuring SFHA 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 SFHA cluster manually
- Setting up non-SCSI-3 fencing in virtual environments manually
- Setting up majority-based I/O fencing manually
- Performing an automated SFHA configuration using response files
- Performing an automated I/O fencing configuration using response files
- Response file variables to configure server-based I/O fencing
- Section III. Upgrade of SFHA
- Planning to upgrade SFHA
- Preparing to upgrade SFHA
- Upgrading Storage Foundation and High Availability
- Performing a rolling upgrade of SFHA
- Performing a phased upgrade of SFHA
- About phased upgrade
- Performing a phased upgrade using the product installer
- Performing an automated SFHA upgrade using response files
- Performing post-upgrade tasks
- Post-upgrade tasks when VCS agents for VVR are configured
- About enabling LDAP authentication for clusters that run in secure mode
- Planning to upgrade SFHA
- Section IV. Post-installation tasks
- Section V. Adding and removing nodes
- Adding a node to SFHA clusters
- Adding the node to a cluster manually
- Adding a node using response files
- Configuring server-based fencing on the new node
- Removing a node from SFHA clusters
- Removing a node from a SFHA cluster
- Removing a node from a SFHA cluster
- Adding a node to SFHA clusters
- Section VI. Configuration and upgrade reference
- Appendix A. Installation scripts
- Appendix B. SFHA services and ports
- Appendix C. Configuration files
- Appendix D. Configuring the secure shell or the remote shell for communications
- Appendix E. Sample SFHA cluster setup diagrams for CP server-based I/O fencing
- Appendix F. Configuring LLT over UDP
- Using the UDP layer for LLT
- Manually configuring LLT over UDP using IPv4
- Using the UDP layer of IPv6 for LLT
- Manually configuring LLT over UDP using IPv6
- Appendix G. 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
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