Please enter search query.
Search <book_title>...
InfoScale™ 9.0 Storage Foundation Cluster File System High Availability Configuration and Upgrade Guide - Solaris
Last Published:
2025-04-21
Product(s):
InfoScale & Storage Foundation (9.0)
Platform: Solaris
- Section I. Introduction to SFCFSHA
- Introducing Storage Foundation Cluster File System High Availability
- Section II. Configuration of SFCFSHA
- Preparing to configure
- Preparing to configure SFCFSHA clusters for data integrity
- About planning to configure I/O fencing
- Setting up the CP server
- Configuring the CP server manually
- Configuring SFCFSHA
- Configuring a secure cluster node by node
- Verifying and updating licenses on the system
- Configuring SFCFSHA clusters for data integrity
- Setting up disk-based I/O fencing using installer
- Setting up server-based I/O fencing using installer
- Performing an automated SFCFSHA configuration using response files
- Performing an automated I/O fencing configuration using response files
- Configuring CP server using response files
- Manually configuring SFCFSHA 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 SFCFSHA cluster manually
- Setting up non-SCSI-3 fencing in virtual environments manually
- Setting up majority-based I/O fencing manually
- Section III. Upgrade of SFCFSHA
- Planning to upgrade SFCFSHA
- Preparing to upgrade SFCFSHA
- Performing a full upgrade of SFCFSHA using the installer
- Performing a rolling upgrade of SFCFSHA
- Performing a phased upgrade of SFCFSHA
- About phased upgrade
- Performing a phased upgrade using the product installer
- Performing an automated SFCFSHA upgrade using response files
- Upgrading Volume Replicator
- Upgrading VirtualStore
- Upgrading SFCFSHA using Boot Environment upgrade
- Performing post-upgrade tasks
- Planning to upgrade SFCFSHA
- Section IV. Post-configuration tasks
- Section V. Configuration of disaster recovery environments
- Section VI. Adding and removing nodes
- Adding a node to SFCFSHA clusters
- Adding the node to a cluster manually
- Setting up the node to run in secure mode
- Adding a node using response files
- Configuring server-based fencing on the new node
- Removing a node from SFCFSHA clusters
- Adding a node to SFCFSHA clusters
- Section VII. Configuration and Upgrade reference
- Appendix A. Installation scripts
- Appendix B. Configuration files
- Appendix C. Configuring the secure shell or the remote shell for communications
- Appendix D. High availability agent information
- Appendix E. Sample SFCFSHA cluster setup diagrams for CP server-based I/O fencing
- Appendix F. Reconciling major/minor numbers for NFS shared disks
- Appendix G. 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
Enabling and disabling rsh for Solaris
The following section describes how to enable remote shell on Solaris system.
Arctera recommends configuring a secure shell environment for InfoScale product installations.
See Manually configuring passwordless ssh.
See the operating system documentation for more information on configuring remote shell.
To enable rsh
- To determine the current status of rsh and rlogin, type the following command:
# inetadm | grep -i login
If the service is enabled, the following line is displayed:
enabled online svc:/network/login:rlogin
If the service is not enabled, the following line is displayed:
disabled disabled svc:/network/login:rlogin
- To enable a disabled rsh/rlogin service, type the following command:
# inetadm -e rlogin
- To disable an enabled rsh/rlogin service, type the following command:
# inetadm -d rlogin
- Modify the .rhosts file. A separate .rhosts file is in the $HOME directory of each user. This file must be modified for each user who remotely accesses the system using rsh. Each line of the .rhosts file contains a fully qualified domain name or IP address for each remote system having access to the local system. For example, if the root user must remotely access sys1 from sys2, you must add an entry for sys2.companyname.com in the .rhosts file on sys1.
# echo "sys2.companyname.com" >> $HOME/.rhosts
- After you complete an installation procedure, delete the .rhosts file from each user's $HOME directory to ensure security:
# rm -f $HOME/.rhosts