Setting up the master metadata server

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.

At this point in the installation, all the metadata servers are equally installed and configured. You need to select one of them to be the master metadata server.

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 lsvpcfg command and make a note of the virtual paths (vpaths) that can be used for metadata disks. You need this information when you are prompted for a list of the metadata disks, as shown towards the end of Table 1. Place an r at the beginning of the vpath name before adding it to the list. For example, if a vpath name is vpatha, the metadata disk is expressed as
    /dev/rvpatha
  3. Run the SAN File System setup utility. You are prompted to enter the information described in Table 1. Accept the defaults for any prompts you see on the screen that are not described in the table.
    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 destroys all metadata stored by the SAN File System.
    Tip: If you are using Active Directory as your LDAP server, you need to run setupsfs using the -debug parameter. Additional prompts are displayed. Enter the appropriate information for the additional LDAP prompts, and accept the defaults for any prompts you see on the screen that are not described in Table 1.
    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 Enter the DN of a user authorized to read the LDAP database, such as the LDAP Administrator or another user in the LDAP directory.
    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 if you used the example LDIF file enter ou=Roles,o=yourOrg .
    LDAP member attribute The attribute that contains the role members. For example if you used the example LDIF file, enter roleOccupant.
    LDAP SSL 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 is 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. For example if you used the example LDIF file without any edits, you would enter Admin.
    CLI password The password defined for the CLI user.
    Truststore password The password that you define to create the truststore and later access it when you copy the truststore from the master metadata server to a subordinate metadata server.
    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/rvpatha /dev/rvpathb /dev/rvpathc /dev/rvpathd. Create this list with the vpaths that you saw when you ran the lsvpcfg command.
  4. When prompted to save the configuration, press Enter. You copy this configuration to the subordinate metadata server engines when you set them up.

Parent topic: Creating the master and subordinate metadata servers

Library | Support | Terms of use | Feedback
(C) Copyright IBM Corporation 2003, 2004. All Rights Reserved.
IBM TotalStorage SAN File System v2.2