Storage Foundation 8.0 Configuration and Upgrade Guide - AIX

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

Configuring DMP support for booting over a SAN

For DMP to work with an LVM root disk over a SAN, configure the system to use the boot device over all possible paths.

To configure DMP support for booting over a SAN

  1. Verify that each path to the root device has the same physical volume identifier (PVID) and the same volume group. Use the lspv command for the root volume group to verify that the PVID and volume group entries are set correctly. The PVID and volume group entries in the second and third columns of the output should be identical for all the paths.

    In this example, the LVM root disk is multi-pathed with four paths. The output from the lspv command for the root volume group (rootvg) is as follows:

    # lspv | grep rootvg
    hdisk374 00cbf5ce56def54d rootvg active
    hdisk375 00cbf5ce56def54d rootvg active
    hdisk376 00cbf5ce56def54d rootvg active
    hdisk377 00cbf5ce56def54d rootvg active
  2. If the PVID and volume group entries are not set correctly on any of the paths, use the chdev command to set the correct value.

    For example, the following output shows that the hdisk377 path is not set correctly:

    # lspv
    hdisk374 00cbf5ce56def54d rootvg active
    hdisk375 00cbf5ce56def54d rootvg active
    hdisk376 00cbf5ce56def54d rootvg active
    hdisk377 none             None

    To set the PVID for the path, use the following command:

    # chdev -l hdisk377 -a pv=yes
    hdisk377 changed

    The output of the lspv command now shows the correct values:

    # lspv | grep rootvg
    hdisk374 00cbf5ce56def54d rootvg active
    hdisk375 00cbf5ce56def54d rootvg active
    hdisk376 00cbf5ce56def54d rootvg active
    hdisk377 00cbf5ce56def54d rootvg active
  3. If any path to the target disk has SCSI reserve ODM attribute set, then change the attributes to release the SCSI reservation from the paths, on a restart.
    • If a path has the reserve_policy attribute set, change thereserve_policy attribute to no_reserve for all the paths.

      # lsattr -E1 hdisk557 | grep res

      reserve_policy single_path

      Reserve Policy True

      # chdev -l hdisk557 -a reserve_policy=no_reserve -P

      hdisk557 changed

    • If a path has the reserve_lock attribute set, change the reserve_lockattribute to no.

      #  lsattr -E1 hdisk558 | grep reserve_lock

      reserve_lock yes

      Reserve Device on open True

      # chdev -l hdisk558 -a reserve_lock=no -P

      hdisk558 changed

  4. Set the boot list to include all the paths of current boot disk.
    # bootlist -m normal hdisk374 hdisk375 hdisk376 hdisk377 blv=hd5

    Verify that the boot list includes all paths and that each path shows the default boot volume hd5:

    # bootlist -m normal -o
    hdisk374 blv=hd5
    hdisk375 blv=hd5
    hdisk376 blv=hd5
    hdisk377 blv=hd5
  5. If the blv option is not set for a path to the disk, use the bootlist command to set it. For example:
    # bootlist -m normal hdisk374 hdisk375 hdisk376 hdisk377 blv=hd5
  6. Run one of the following commands to configure DMP on the root disk:
    • The recommended method is to turn on DMP support for LVM volumes, including the root volume.

      # vxdmpadm settune dmp_native_support=on
    • The following command enables DMP support for LVM volumes only for the root disk.

      # vxdmpadm native enable vgname=rootvg
  7. Reboot the system. DMP takes control of the SAN boot device to perform load balancing and failover.
  8. Verify whether DMP controls the root disk.
    # vxdmpadm native list vgname=rootvg
    PATH           DMPNODENAME
    ===========================
    hdisk374       ams_wms0_491
    hdisk375       ams_wms0_491
    hdisk376       ams_wms0_491
    hdisk377       ams_wms0_491
    # lspv | grep rootvg
    hdisk374 00cbf5ce56def54d rootvg active
    hdisk375 00cbf5ce56def54d rootvg active
    hdisk376 00cbf5ce56def54d rootvg active
    hdisk377 00cbf5ce56def54d rootvg active