Please enter search query.
Search <book_title>...
Storage Foundation 7.2 Configuration and Upgrade Guide - Solaris
Last Published:
2018-03-06
Product(s):
InfoScale & Storage Foundation (7.2)
Platform: Solaris
- Section I. Introduction and configuration of Storage Foundation
- Section II. Upgrade of Storage Foundation
- Planning to upgrade Storage Foundation
- Preparing to upgrade SF
- Upgrading Storage Foundation
- Performing an automated SF upgrade using response files
- Upgrading SF using Boot Environment upgrade
- Performing post-upgrade tasks
- Upgrading the Array Support Library
- Planning to upgrade Storage Foundation
- Section III. Post configuration tasks
- Section IV. Configuration and Upgrade reference
- Appendix A. Installation scripts
- Appendix B. Configuring the secure shell or the remote shell for communications
Enabling and disabling rsh for Solaris
The following section describes how to enable remote shell on Solaris system.
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
- 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