Storage Foundation 7.4.2 Configuration and Upgrade Guide - AIX

Last Published:
Product(s): InfoScale & Storage Foundation (7.4.2)
Platform: AIX
  1. Section I. Introduction and configuration of Storage Foundation
    1. Introducing Storage Foundation
      1. About Storage Foundation
          About Veritas Replicator Option
        About Veritas InfoScale Operations Manager
        About Veritas Services and Operations Readiness Tools (SORT)
    2. Configuring Storage Foundation
        Configuring Storage Foundation using the installer
      2. Configuring SF manually
          Configuring Veritas File System
        Configuring DMP support for booting over a SAN
        Configuring SFDB
  2. Section II. Upgrade of Storage Foundation
    1. Planning to upgrade Storage Foundation
        About the upgrade
        Supported upgrade paths
      3. Preparing to upgrade SF
          Getting ready for the upgrade
          Preparing for an upgrade of Storage Foundation
          Creating backups
        4. Pre-upgrade planning when VVR is configured
            Considerations for upgrading SF to 7.4 or later on systems with an ongoing or a paused replication
          2. Planning an upgrade from the previous VVR version
              Planning and upgrading VVR to use IPv6 as connection protocol
          Verifying that the file systems are clean
          Upgrading the array support
        Using Install Bundles to simultaneously install or upgrade full releases (base, maintenance, rolling patch), and individual patches
    2. Upgrading Storage Foundation
        Upgrading Storage Foundation with the product installer
      2. Upgrade Storage Foundation and AIX on a DMP-enabled rootvg
          Upgrading from prior version of SF on AIX 7.1 to SF 7.4.2 on a DMP-enabled rootvg
          Upgrading the operating system from AIX 7.1 to AIX 7.2 in Veritas InfoScale 7.4.2
        Upgrading SF on a Virtual I/O server (VIOS) from 6.2.1 or later to 7.4.2
        Upgrading the AIX operating system
      5. Upgrading Volume Replicator
        1. Upgrading VVR without disrupting replication
            Upgrading VVR on the Secondary
            Upgrading VVR on the Primary
        Upgrading SFDB
    3. Performing an automated SF upgrade using response files
        Upgrading SF using response files
        Response file variables to upgrade SF
        Sample response file for SF upgrade
    4. Performing post-upgrade tasks
        Optional configuration steps
        Recovering VVR if automatic upgrade fails
        Resetting DAS disk names to include host name in FSS environments
        Upgrading disk layout versions
        Upgrading VxVM disk group versions
        Updating variables
        Setting the default disk group
        Verifying the Storage Foundation upgrade
  3. Section III. Post configuration tasks
    1. Performing configuration tasks
        Switching on Quotas
        Enabling DMP support for native devices
      3. About configuring authentication for SFDB tools
          Configuring vxdbd for SFDB tools authentication
  4. Section IV. Configuration and Upgrade reference
    1. Appendix A. Support for AIX Live Update
        Support for AIX Live Update (Technology preview)
    2. Appendix B. Installation scripts
        Installation script options
        About using the postcheck option
    3. Appendix C. Configuring the secure shell or the remote shell for communications
        About configuring secure shell or remote shell communication modes before installing products
        Manually configuring passwordless ssh
        Setting up ssh and rsh connection using the installer -comsetup command
        Setting up ssh and rsh connection using the utility
        Restarting the ssh session
        Enabling rsh for AIX
    4. Appendix D. Changing NFS server major numbers for VxVM volumes
        Changing NFS server major numbers for VxVM volumes

Manually configuring passwordless ssh

The ssh program enables you to log into and execute commands on a remote system. ssh enables encrypted communications and an authentication process between two untrusted hosts over an insecure network.

In this procedure, you first create a DSA key pair. From the key pair, you append the public key from the source system to the authorized_keys file on the target systems.

Figure: Creating the DSA key pair and appending it to target systems illustrates this procedure.

Figure: Creating the DSA key pair and appending it to target systems

Creating the DSA key pair and appending it to target systems

Read the ssh documentation and online manual pages before enabling ssh. Contact your operating system support provider for issues regarding ssh configuration.

Visit the Openssh website that is located at: to access online manuals and other resources.

To create the DSA key pair

  1. On the source system (sys1), log in as root, and navigate to the root directory.
    sys1 # cd /
  2. Make sure the /.ssh directory is on all the target installation systems (sys2 in this example). If that directory is not present, create it on all the target systems and set the write permission to root only:

    Change the permissions of this directory, to secure it.

  3. To generate a DSA key pair on the source system, type the following command:
    sys1 # ssh-keygen -t dsa

    System output similar to the following is displayed:

    Generating public/private dsa key pair.
    Enter file in which to save the key (//.ssh/id_dsa):
  4. Press Enter to accept the default location of /.ssh/id_dsa.
  5. When the program asks you to enter the passphrase, press the Enter key twice.
    Enter passphrase (empty for no passphrase):

    Do not enter a passphrase. Press Enter.

    Enter same passphrase again:

    Press Enter again.

To append the public key from the source system to the authorized_keys file on the target system, using secure file transfer

  1. From the source system (sys1), move the public key to a temporary file on the target system (sys2).

    Use the secure file transfer program.

    In this example, the file name in the root directory is the name for the temporary file for the public key.

    Use the following command for secure file transfer:

    sys1 # sftp sys2

    If the secure file transfer is set up for the first time on this system, output similar to the following lines is displayed:

    Connecting to sys2 ...
    The authenticity of host 'sys2 (' 
    can't be established. DSA key fingerprint is
    Are you sure you want to continue connecting (yes/no)?
  2. Enter yes.

    Output similar to the following is displayed:

    Warning: Permanently added 'sys2,' 
    (DSA) to the list of known hosts.
    root@sys2 password:
  3. Enter the root password of sys2.
  4. At the sftp prompt, type the following command:
    sftp> put /.ssh/

    The following output is displayed:

    Uploading /.ssh/ to /
  5. To quit the SFTP session, type the following command:
    sftp> quit
  6. To begin the ssh session on the target system (sys2 in this example), type the following command on sys1:
    sys1 # ssh sys2

    Enter the root password of sys2 at the prompt:

  7. After you log in to sys2, enter the following command to append the file to the authorized_keys file:
    sys2 # cat / >> /.ssh/authorized_keys
  8. After the public key file is copied to the target system (sys2), and added to the authorized keys file, delete it. To delete the public key file, enter the following command on sys2:
    sys2 # rm /
  9. To log out of the ssh session, enter the following command:
    sys2 # exit
  10. Run the following commands on the source installation system. If your ssh session has expired or terminated, you can also run these commands to renew the session. These commands bring the private key into the shell environment and make the key globally available to the user root:
    sys1 # exec /usr/bin/ssh-agent $SHELL
    sys1 # ssh-add
      Identity added: //.ssh/id_dsa

    This shell-specific step is valid only while the shell is active. You must execute the procedure again if you close the shell during the session.

To verify that you can connect to a target system

  1. On the source system (sys1), enter the following command:
    sys1 # ssh -l root sys2 uname -a

    where sys2 is the name of the target system.

  2. The command should execute from the source system (sys1) to the target system (sys2) without the system requesting a passphrase or password.
  3. Repeat this procedure for each target system.