This task describes how to use the setupsfs utility to set up the master metadata server.
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.
/dev/rvpatha
/usr/tank/admin/bin/setupsfs -setmaster
/usr/tank/admin/bin/setupsfs -setmaster -overwrite
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. |
Parent topic: Creating the master and subordinate metadata servers