Configuration steps after expansion

Contributors netapp-madkat netapp-perveilerk netapp-pcelmer

After completing an expansion, you must perform additional integration and configuration steps.

About this task

You must complete the configuration tasks listed below for the grid nodes you are adding in your expansion. Some tasks might be optional, depending on the options selected when installing and administering your system, and how you want to configure the grid nodes added during the expansion.

Steps
  1. If you added a Storage Node, complete the following configuration tasks:

    1. Review the storage pools used in your ILM rules to ensure the new storage will be used. See Manage objects with ILM.

      • If you added a site, create a storage pool for the site and update ILM rules to use the new storage pool.

      • If you added a Storage Node to an existing site, confirm that the new node uses the correct storage grade.

        Note By default, a new Storage Node is assigned to the All Storage Nodes storage grade and added to storage pools that use that grade for the site. If you want a new node to use a custom storage grade, you must assign it to the custom grade manually (ILM > Storage grades).
    2. Verify that the Storage Node is ingesting objects. See Verify that the Storage Node is active.

    3. Rebalance erasure-coded data (only if you were unable to add the recommended number of Storage Nodes). See Rebalance erasure-coded data after adding Storage Nodes.

  2. If you added a Gateway Node, complete the following configuration task:

    • If high availability (HA) groups are used for client connections, optionally add the Gateway Node to an HA group. Select CONFIGURATION > Network > High availability groups to review the list of existing HA groups and to add the new node. See Administer StorageGRID.

  3. If you added an Admin Node, complete the following configuration tasks:

    1. If single sign-on (SSO) is enabled for your StorageGRID system, create a relying party trust for the new Admin Node. You cannot sign in to the node until you create this relying party trust. See Configure single sign-on.

    2. If you plan to use the Load Balancer service on Admin Nodes, optionally add the new Admin Node to a HA group. Select CONFIGURATION > Network > High availability groups to review the list of existing HA groups and to add the new node. See Administer StorageGRID.

    3. Optionally, copy the Admin Node database from the primary Admin Node to the expansion Admin Node if you want to keep the attribute and audit information consistent on each Admin Node. See Copy the Admin Node database.

    4. Optionally, copy the Prometheus database from the primary Admin Node to the expansion Admin Node if you want to keep the historical metrics consistent on each Admin Node. See Copy Prometheus metrics.

    5. Optionally, copy the existing audit logs from the primary Admin Node to the expansion Admin Node if you want to keep the historical log information consistent on each Admin Node. See Copy audit logs.

    6. Optionally, configure access to the system for auditing purposes through an NFS or a CIFS file share. See Administer StorageGRID.

      Note Audit export through CIFS/Samba has been deprecated and will be removed in a future StorageGRID release.
    7. Optionally, change the preferred sender for notifications. You can make the expansion Admin Node the preferred sender. Otherwise, an existing Admin Node configured as the preferred sender continues to send notifications, including AutoSupport messages, SNMP notifications, alert emails, and alarm emails (legacy system). See Administer StorageGRID.

  4. If you added an Archive Node, complete the following configuration tasks.

    1. Configure the Archive Node’s connection to the targeted external archival storage system. When you complete the expansion, Archive Nodes are in an alarm state until you configure connection information through the ARC > Target component. See Administer StorageGRID.

    2. Update the ILM policy to archive object data through the new Archive Node. See Manage objects with ILM.

    3. Configure custom alarms for the attributes that are used to monitor the speed and efficiency of object data retrieval from Archive Nodes. See Administer StorageGRID.

  5. To check if expansion nodes were added with an untrusted Client Network or to change whether a node’s Client Network is untrusted or trusted, go to CONFIGURATION > Network > Untrusted Client Network.

    If the Client Network on the expansion node is untrusted, then connections to the node on the Client Network must be made using a load balancer endpoint. See Administer StorageGRID.

  6. Configure the Domain Name System (DNS).

    If you have been specifying DNS settings separately for each grid node, you must add custom per-node DNS settings for the new nodes. See Modify DNS configuration for single grid node.

    The best practice is for the grid-wide DNS server list to contain some DNS servers that are accessible locally from each site. If you just added a new site, add new DNS servers for the site to the grid-wide DNS configuration.

    Important Provide two to six IPv4 addresses for DNS servers. You should select DNS servers that each site can access locally in the event of network islanding. This is to ensure an islanded site continues to have access to the DNS service. After configuring the grid-wide DNS server list, you can further customize the DNS server list for each node. For details, see Modify DNS configuration for single grid node..
  7. If you added a new site, confirm that Network Time Protocol (NTP) servers are accessible from that site. See Configure NTP servers.

    Important Make sure that at least two nodes at each site can access at least four external NTP sources. If only one node at a site can reach the NTP sources, timing issues will occur if that node goes down. In addition, designating two nodes per site as primary NTP sources ensures accurate timing if a site is isolated from the rest of the grid.