Summary: IP addresses and ports for client connections

Client applications can connect to StorageGRID using the IP address of a grid node and the port number of a service on that node. If high availability (HA) groups are configured, client applications can connect using the virtual IP address of the HA group.

About this task

This table summarizes the different ways that clients can connect to StorageGRID and the IP addresses and ports that are used for each type of connection. The instructions describe how to find this information in the Grid Manager if load balancer endpoints and high availability (HA) groups are already configured.

Where connection is made Service that client connects to IP address Port
HA group Load Balancer Virtual IP address of an HA group
  • Load balancer endpoint port
HA group CLB
Note: The CLB service is deprecated.
Virtual IP address of an HA group Default S3 ports:
  • HTTPS: 8082
  • HTTP: 8084
Default Swift ports:
  • HTTPS:8083
  • HTTP:8085
Admin Node Load Balancer IP address of the Admin Node
  • Load balancer endpoint port
Gateway Node Load Balancer IP address of the Gateway Node
  • Load balancer endpoint port
Gateway Node CLB
Note: The CLB service is deprecated.
IP address of the Gateway Node
Note: By default, HTTP ports for CLB and LDR are not enabled.
Default S3 ports:
  • HTTPS: 8082
  • HTTP: 8084
Default Swift ports:
  • HTTPS:8083
  • HTTP:8085
Storage Node LDR IP address of Storage Node Default S3 ports:
  • HTTPS: 18082
  • HTTP: 18084
Default Swift ports:
  • HTTPS: 18083
  • HTTP:18085

Examples

To connect an S3 client to the Load Balancer endpoint of an HA group of Gateway Nodes, use a URL structured as shown below:

For example, if the virtual IP address of the HA group is 192.0.2.5 and the port number of an S3 Load Balancer endpoint is 10443, then an S3 client could use the following URL to connect to StorageGRID: To connect a Swift client to the Load Balancer endpoint of an HA group of Gateway Nodes, use a URL structured as shown below: For example, if the virtual IP address of the HA group is 192.0.2.6 and the port number of a Swift Load Balancer endpoint is 10444, then a Swift client could use the following URL to connect to StorageGRID: It is possible to configure a DNS name for the IP address that clients use to connect to StorageGRID. Contact your local network administrator.

Procedure

  1. Sign in to the Grid Manager using a supported browser.
  2. To find the IP address of a grid node:
    1. Select Nodes.
    2. Select the Admin Node, Gateway Node, or Storage Node to which you want to connect.
    3. Select the Overview tab.
    4. In the Node Information section, note the IP addresses for the node.
    5. Click Show more to view IPv6 addresses and interface mappings.
      You can establish connections from client applications to any of the IP addresses in the list:
      • eth0: Grid Network
      • eth1: Admin Network (optional)
      • eth2: Client Network (optional)
        Note: If you are viewing an Admin Node or a Gateway Node and it is the active node in a high availability group, the virtual IP address of the HA group is shown on eth2.
  3. To find the virtual IP address of a high availability group:
    1. Select Configuration > Network Settings > High Availability Groups.
    2. In the table, note the virtual IP address of the HA group.
  4. To find the port number of a Load Balancer endpoint:
    1. Select Configuration > Network Settings > Load Balancer Endpoints.
      The Load Balancer Endpoints page appears, showing the list of endpoints that have already been configured.
    2. Select an endpoint, and click Edit endpoint.
      The Edit Endpoint window opens and displays additional details about the endpoint.
    3. Confirm that the endpoint you have selected is configured for use with the correct protocol (S3 or Swift), then click Cancel.
    4. Note the port number for the endpoint that you want to use for a client connection.
      Note: If the port number is 80 or 443, the endpoint is configured only on Gateway Nodes, since those ports are reserved on Admin Nodes. All other ports are configured on both Gateway Nodes and Admin Nodes.