Approving pending grid nodes

You must approve each grid node before it joins the StorageGRID Webscale grid.

Before you begin

All virtual and StorageGRID Webscale appliance grid nodes must have been deployed.

Steps

  1. Review the Pending Nodes list, and confirm that it shows all of the grid nodes you deployed.
    Note: If a grid node is missing, confirm that it was deployed successfully.
  2. Select the radio button next to a pending node you want to approve.

    This image is explained by the surrounding text.
  3. Click Approve.
  4. In General Settings, modify settings for the following properties, as necessary:

    This image is explained by the surrounding text.
    • Site: The name of the site with which this grid node will be associated.
    • Name: The host name that will be assigned to the node, and the name that will be displayed in the Grid Manager. The name defaults to the name you specified during node deployment, but you can change the name here as required.
    • NTP Role: The Network Time Protocol (NTP) role of the grid node. The options are Automatic, Primary, and Client. Selecting Automatic assigns the Primary role to Admin Nodes, Storage Nodes with ADC services, API Gateway Nodes, and any grid nodes that have non-static IP addresses. All other grid nodes are assigned the Client role.
      Attention: 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.
    • ADC service: For Storage Nodes, whether the selected node will run the Administrative Domain Controller service. Select Automatic to have the this option applied automatically by the system as required, or select Yes or No to explicitly set this option for the grid node. For example, you might need to select Yes if you want to have more than three ADC services at a site.
  5. In Grid Network, modify settings for the following properties as necessary:
    • IPv4 Address (CIDR): The CIDR network address for the eth0 Grid Network interface. For example: 192.168.1.234/21
    • Gateway: The Grid Network gateway. For example: 192.168.0.1
    Note: The gateway is required if there are multiple grid subnets.
  6. If you want to configure the Admin Network for the grid node, add or update the settings in the Admin Network section as necessary.
    Enter the destination subnets of the routes out of this interface in the Subnets (CIDR) text box. If there are multiple Admin subnets, the Admin gateway is required.
    Note: If you selected DHCP for the Admin Network configuration and you change the value here, the new value will be configured as a static address on the node. You must make sure the resulting IP address is not within a DHCP address pool.
  7. If you want to configure the Client Network for the grid node, add or update the settings in the Client Network section as necessary. If the Client Network is configured, the gateway is required, and it becomes the default gateway for the node after installation.
    Note: If you selected DHCP for the Client Network configuration and you change the value here, the new value will be configured as a static address on the node. You must make sure the resulting IP address is not within a DHCP address pool.
  8. Click Save.
    The grid node entry moves to the Approved Nodes list.


    This image is explained by the surrounding text.

  9. Repeat these steps for each pending grid node you want to approve.
    You must approve all nodes that you want in the grid. However, you can return to this page at any time before you click Install on the Summary page. You can modify the properties of an approved grid node by selecting its radio button and clicking Edit.
  10. When you are done approving grid nodes, click Next.