Veritas InfoScale™ 7.3.1 Installation Guide - AIX

Last Published:
Product(s): InfoScale & Storage Foundation (7.3.1)
  1. Section I. Introduction to Veritas InfoScale
    1. Introducing Veritas InfoScale
      1.  
        About the Veritas InfoScale product suite
      2.  
        About Veritas InfoScale Foundation
      3.  
        About Veritas InfoScale Storage
      4.  
        About Veritas InfoScale Availability
      5.  
        About Veritas InfoScale Enterprise
      6.  
        Components of the Veritas InfoScale product suite
    2. Licensing Veritas InfoScale
      1.  
        About Veritas InfoScale product licensing
      2.  
        Registering Veritas InfoScale using product license keys
      3.  
        Registering Veritas InfoScale product using keyless licensing
      4.  
        Updating your product licenses
      5.  
        Using the vxlicinstupgrade utility
      6.  
        About the VRTSvlic package
  2. Section II. Planning and preparation
    1. System requirements
      1.  
        Important release information
      2.  
        Disk space requirements
      3. Hardware requirements
        1.  
          SF and SFHA hardware requirements
        2.  
          SFCFS and SFCFSHA hardware requirements
        3.  
          SF Oracle RAC hardware requirements
        4.  
          VCS hardware requirements
        5.  
          Virtual I/O Server (VIOS) requirements
      4.  
        Supported operating systems and database versions
      5.  
        Number of nodes supported
    2. Preparing to install
      1.  
        Mounting the ISO image
      2.  
        Setting up ssh or rsh for inter-system communications
      3.  
        Obtaining installer patches
      4.  
        Disabling external network connection attempts
      5.  
        Verifying the systems before installation
      6. Setting up the private network
        1.  
          Optimizing LLT media speed settings on private NICs
        2.  
          Guidelines for setting the media speed for LLT interconnects
        3.  
          Guidelines for setting the maximum transmission unit (MTU) for LLT interconnects in Flexible Storage Sharing (FSS) environments
      7. Setting up shared storage
        1.  
          Setting the SCSI identifier value
        2.  
          Setting up Fibre Channel
      8.  
        Synchronizing time settings on cluster nodes
      9.  
        Configuring LLT interconnects to use Jumbo Frames
      10. Planning the installation setup for SF Oracle RAC systems
        1. Planning your network configuration
          1.  
            Planning the public network configuration for Oracle RAC
          2. Planning the private network configuration for Oracle RAC
            1.  
              High availability solutions for Oracle RAC private network
          3.  
            Planning the public network configuration for Oracle RAC
          4.  
            Planning the private network configuration for Oracle RAC
        2. Planning the storage
          1.  
            Planning the storage
          2. Planning the storage for Oracle RAC
            1. Planning the storage for OCR and voting disk
              1.  
                OCR and voting disk storage configuration for external redundancy
              2.  
                OCR and voting disk storage configuration for normal redundancy
            2.  
              Planning the storage for Oracle RAC binaries and data files
            3.  
              Planning for Oracle RAC ASM over CVM
        3.  
          Planning volume layout
        4.  
          Planning file system design
        5.  
          Setting the umask before installation
      11.  
        Updating the SCSI reserve ODM attribute settings for VIOS
  3. Section III. Installation of Veritas InfoScale
    1. Installing Veritas InfoScale using the installer
      1.  
        Installing Veritas InfoScale using the installer
    2. Installing Veritas InfoScale using response files
      1. About response files
        1.  
          Syntax in the response file
      2.  
        Installing Veritas InfoScale using response files
      3.  
        Response file variables to install Veritas InfoScale
      4.  
        Sample response file for Veritas InfoScale installation
    3. Installing Veritas Infoscale using operating system-specific methods
      1.  
        About installing Veritas InfoScale using operating system-specific methods
      2. Installing Veritas InfoScale using NIM and the installer
        1.  
          Preparing the installation bundle on the NIM server
        2.  
          Installing Veritas InfoScale on the NIM client using SMIT on the NIM server
        3.  
          Installing Veritas InfoScale and the operating system on the NIM client using SMIT
    4. Completing the post installation tasks
      1.  
        Verifying product installation
      2.  
        Setting environment variables
      3.  
        Next steps after installation
  4. Section IV. Uninstallation of Veritas InfoScale
    1. Uninstalling Veritas InfoScale using the installer
      1. Preparing to uninstall a Veritas InfoScale product
        1.  
          Moving volumes to physical disks
      2.  
        Removing the Replicated Data Set
      3.  
        Uninstalling Veritas InfoScale filesets using the installer
      4.  
        Removing Storage Foundation products using SMIT
      5.  
        Removing the Storage Foundation for Databases (SFDB) repository
    2. Uninstalling Veritas InfoScale using response files
      1.  
        Uninstalling Veritas InfoScale using response files
      2.  
        Response file variables to uninstall Veritas InfoScale
      3.  
        Sample response file for Veritas InfoScale uninstallation
  5. Section V. Installation reference
    1. Appendix A. Installation scripts
      1.  
        Installation script options
    2. Appendix B. Tunable files for installation
      1.  
        About setting tunable parameters using the installer or a response file
      2.  
        Setting tunables for an installation, configuration, or upgrade
      3.  
        Setting tunables with no other installer-related operations
      4.  
        Setting tunables with an un-integrated response file
      5.  
        Preparing the tunables file
      6.  
        Setting parameters for the tunables file
      7.  
        Tunables value parameter definitions
    3. Appendix C. Troubleshooting installation issues
      1.  
        Restarting the installer after a failed network connection
      2.  
        Troubleshooting an installation on AIX
      3.  
        Incorrect permissions for root on remote system
      4.  
        Resource temporarily unavailable
      5.  
        Inaccessible system

Planning the private network configuration for Oracle RAC

Oracle RAC requires a minimum of one private IP address on each node for Oracle Clusterware heartbeat.

For a11g and later versions, you must use UDP IPC for the database cache fusion traffic.

Veritas recommends using multiple private interconnects for load balancing the cache fusion traffic.

Note:

The private IP addresses of all nodes that are on the same physical network must be in the same IP subnet.

The following practices provide a resilient private network setup:

  • Configure Oracle Clusterware interconnects over LLT links to prevent data corruption.

    In an Veritas InfoScale cluster, the Oracle Clusterware heartbeat link MUST be configured as an LLT link. If Oracle Clusterware and LLT use different links for their communication, then the membership change between VCS and Oracle Clusterware is not coordinated correctly. For example, if only the Oracle Clusterware links are down, Oracle Clusterware kills one set of nodes after the expiry of the css-misscount interval and initiates the Oracle Clusterware and database recovery, even before CVM and CFS detect the node failures. This uncoordinated recovery may cause data corruption.

  • Oracle Clusterware interconnects need to be protected against NIC failures and link failures. For Oracle RAC 11.2.0.1 versions, the PrivNIC or MultiPrivNIC agent can be used to protect against NIC failures and link failures, if multiple links are available. Even if link aggregation solutions in the form of bonded NICs are implemented, the PrivNIC or MultiPrivNIC agent can be used to provide additional protection against the failure of the aggregated link by failing over to available alternate links. These alternate links can be simple NIC interfaces or bonded NICs.

    An alternative option is to configure the Oracle Clusterware interconnects over bonded NIC interfaces.

    See High availability solutions for Oracle RAC private network.

    Note:

    The PrivNIC and MultiPrivNIC agents are no longer supported in Oracle RAC 11.2.0.2 and later versions for managing cluster interconnects.

    For 11.2.0.2 and later versions, Veritas recommends the use of alternative solutions such as bonded NIC interfaces or Oracle High Availability IP (HAIP).

  • Configure Oracle Cache Fusion traffic to take place through the private network. Veritas also recommends that all UDP cache-fusion links be LLT links.

    For Oracle RAC 11.2.0.1 versions, the PrivNIC and MultiPrivNIC agents provide a reliable alternative when operating system limitations prevent you from using NIC bonding to provide high availability and increased bandwidth using multiple network interfaces. In the event of a NIC failure or link failure, the agent fails over the private IP address from the failed link to the connected or available LLT link. To use multiple links for database cache fusion for increased bandwidth, configure the cluster_interconnects initialization parameter with multiple IP addresses for each database instance and configure these IP addresses under MultiPrivNIC for high availability.

    Oracle database clients use the public network for database services. Whenever there is a node failure or network failure, the client fails over the connection, for both existing and new connections, to the surviving node in the cluster with which it is able to connect. Client failover occurs as a result of Oracle Fast Application Notification, VIP failover and client connection TCP timeout. It is strongly recommended not to send Oracle Cache Fusion traffic through the public network.

  • Use NIC bonding to provide redundancy for public networks so that Oracle RAC can fail over virtual IP addresses if there is a public link failure.