Running the SAN File System setup utility

This task describes how to use the setupsfs utility to set up the master metadata server.

Prerequisites

All of the software should be loaded on the metadata server before you set it up as the master metadata server. The LDAP server should also be available. In addition, if you are using secured LDAP, the LDAP public certificate file should be copied to /usr/tank/admin.

Context

The setupsfs utility is used to start the SAN File System metadata server configuration process.

Steps

  1. Make sure that you are logged in as root.
  2. Run the SAN File System setup utility.
    1. If you are using system disks that have not previously been used with the SAN File System, run the setup utility as follows:
      /usr/tank/admin/bin/setupsfs -setmaster 
    2. If you are using system disks that were previously used with SAN File System and you want to completely re-initialize those disks, run the setup utility as follows:
      /usr/tank/admin/bin/setupsfs -setmaster -overwrite 
      Attention: You can use the -overwrite parameter to initialize the given master metadata server and system disks, regardless of whether they already contain cluster information. For example, if you get a failure in log.std indicating that the metadata disk is already labeled, but you are sure you wish to reuse that disk, you can rerun the setupsfs command with the -overwrite parameter. Remember that this parameter will destroy all metadata stored by the SAN File System.
    Tip: If you are using ActiveDirectory as your LDAP server, you need to run setupsfs using the -debug parameter. Additional prompts will be displayed. Enter the appropriate information for the additional LDAP prompts, and accept the defaults for the additional prompts.
    You will be prompted to enter the following information.
    Table 1. Setupsfs prompts
    Value Description
    SAN File System Server name A unique name to be used for this metadata server engine. This name must be the same as the unique name used to configure the RSA II adapter on each engine.
    SAN File System Cluster name The name of the SAN File System cluster.
    Server IP address The IP address of the metadata server engine in dotted-decimal format.
    Language The language locale. For example, en_US.utf8
    LDAP server IP address The IP address of the LDAP server in dotted-decimal format.
    LDAP user The distinguished name of an authorized LDAP user. For example, cn=root
    LDAP user password The password for the LDAP user. This password must match the password set for this user in the LDAP server database.
    LDAP secured connection Set this value to true if you are using secured LDAP. Otherwise, set this value to false.
    LDAP base distinguished name The base distinguished name used to search for roles. For example, ou=NewRoles,o=ibm,c=US
    LDAP member attribute The attribute that contains the role members. For example, roleOccupant
    LDAP certificate If you are using secured LDAP, provide the fully qualified name of the LDAP certificate, which was obtained from the LDAP server. For example, /tmp/ldap.cert.
    Note: When you run setupsfs, this certificate will be embedded in the truststore.
    RSA user name The user ID used to access the RSA II adapter. The default is USERID.
    RSA password The passed for the user ID. The default is PASSW0RD (0 is zero).
    CLI user A user ID that has access to the administrative command-line interface. This user ID must be defined in the LDAP server database and must be set to the role of administrator.
    CLI password The password defined for the CLI user.
    Truststore password The password used to access the truststore.
    Subordinate node list A space-separated list of the IP addresses for subordinate metadata server engines in the cluster. For example, 192.168.10.69 192.168.10.79 192.168.10.89
    Metadata disks A space-separated list of raw devices on which SAN File System metadata is stored. For example, /dev/rvpathao /dev/rvpathap /dev/rvpathaq /dev/rvpathar.
    You can run the lsvpcfg command to decide which vpaths can be used for metadata disks. Then, you can specify the devices for this parameter using the following syntax:
    /dev/rvpath.
  3. When prompted to save the configuration, press Enter. You will copy this configuration to the subordinate metadata server engines when you set them up.

Parent topic: Setting up the master metadata server

Terms of use | Feedback
(C) Copyright IBM Corporation 2003, 2004. All Rights Reserved.