Configuring Storage Foundation Cluster File System

This section describes configuring Storage Foundation Cluster File System using the Veritas product installer. If you configured Storage Foundation Cluster File System during the installation process, you do not need to perform the procedure in this section.

To configure the product, run the Veritas product installer or the appropriate installation script using the -configure option.

To configure Storage Foundation Cluster File System

  1. To invoke the common installer, run the installer command with the configure option, as shown in this example:

    # ./installer -configure
  2. When the list of available products is displayed, select Veritas Storage Foundation Cluster File System (SFCFS), or Veritas Storage Foundation Cluster File System High Availability (SFCFS HA), enter the corresponding number, and press Return.

    Select a product to configure:
  3. You are prompted to enter the system names (in the following example, "system01" and "system02") on which the software is to be installed. Enter the system name or names and then press Return.

    Enter the system names separated by spaces on which to 
    configure SFCFS: system01 system02
  4. During the initial system check, the installer checks that communication between systems has been set up.

    The installer requires that ssh commands used between systems execute without prompting for passwords or confirmations. If the installer hangs or asks for a login password, stop the installer and run it again with the ssh configured for password free logins, or configure rsh and use the -rsh option.

    See Configuring secure shell (ssh) or remote shell before installing products.

  5. The procedure checks system licensing, and you can enter additional licenses, if needed.

    Checking system licensing
    
    SFCFS license registered on system01
    
    Do you want to enter another license key for system01? 
    [y,n,q] (n) n
  6. Any running SFCFS processes are stopped. Press Return to continue.

  7. Starting I/O Fencing in enabled mode requires manual intervention after SFCFS Configuration. I/O Fencing can be configured in disabled mode now and it does not require any manual intervention after SFCFS Configuration.

    Determine at this time if you plan to configure I/O Fencing in enabled mode or disabled mode, as well as the number of network interconnects (NICS) required on your systems. If you configure I/O Fencing in enabled mode only a single NIC is required, though at least two is recommended.

    Enter y or n for configuring I/O Fencing in enabled mode.

    Will you be configuring I/O Fencing in enabled mode? 
    [y,n,q,?] (y) n

    See the Storage Foundation Cluster File System Administrator's Guide for more information.

  8. No configuration changes are made to the systems until all configuration questions are completed and confirmed. Press Return to continue.

    All systems are configured to create one cluster.

    Enter the unique cluster name and Cluster ID number.

    Enter the unique cluster name: [?]cluster2
    Enter the unique Cluster ID number between 0-65535: [b,?] 76
  9. The installer discovers the NICs available on the first system and reports them.

    Discovering NICs on host1 ...discovered bge0 bge1 bge2 bge3
  10. To use aggregated interfaces for private heartbeat, enter the name of an aggregated interface. To use a NIC for private heartbeat, enter a NIC which is not part of an aggregated interface.

    Enter private heartbeat NIC information for each host.

    Enter the NIC for the first private heartbeat link 
    on host1: [b,?] bge1
    bge1 has an IP address configured on it. It could be a public NIC on
    system01.
    Are you sure you want to use bge1 for the first private heartbeat link?
    [y,n,q,b,?] (n) y
    Is bge1 a bonded NIC? [y,n,q] (n) n
    Would you like to configure a second private heartbeat link? [y,n,q,b,?] (y)
    Enter the NIC for the second private heartbeat link on system01: [b,q,?] bge2
    bge2 has an IP address configured on it. It could be a public NIC on
    system01.
    Are you sure you want to use bge2 for the second private heartbeat link?
    [y,n,q,b,?] (n) y
    Is bge2 a bonded NIC? [y,n,q] (n)
    Would you like to configure a third private heartbeat 
    link? [y,n,q,b,?] (n) n
    Do you want to configure an additional low priority 
    heartbeat link? [y,n,q,b,?] (n) n
    Are you using the same NICs for private heartbeat links 
    on all systems? [y,n,q,b,?] (y) y

    Warning:

    When answering y, be sure that the same NICs are available on each system; the installer may not verify this.

    Notice that in this example, bge0 is not selected for use as a private heartbeat NIC because it already in use as the public network interface.

  11. A summary of the information you entered is given. When prompted, confirm that the information is correct.

    Is this information correct? [y,n,q]

    If the information is correct, enter y. If the information is not correct, enter n. The installer prompts you to enter the information again.

  12. At the prompt, specify whether you want to send your installation information to Symantec.

    Would you like to send the information about this installation to Symantec to help improve installation in the future? [y,n,q,?] (y) n

  13. The Veritas Storage Foundation Cluster File System software is verified and configured.

    Check the log file, if needed, to confirm the configuration.

    Configuration log files, summary file, and response file are saved at:
    
            /opt/VRTS/install/logs/installer-****
  14. The installation script prompts for a reboot if there are one or more errors. Reboot the system (or systems) if the install script prompts you to do so.

  15. If you do not plan to use SFCFS file systems to store the Oracle database or binaries, you have completed the SFCFS installation and configuration.

    Before installing Oracle binaries (ORACLE_HOME), consider these points:

    • Local installations provide a comfort level using traditional installation methods and the possibility of improved protection against a single point of failure.

    • CFS installations provide a single Oracle installation to manage, regardless of number of nodes. This scenario offers a necessary reduction in storage requirements and easy addition of nodes.

    Select the location based on your high availability requirements. Symantec generally recommends using local installations.

    See the Veritas Storage Foundation Cluster File System Administrator's Guide for more information on Oracle Disk Manager.