Skip to main content

Assessing networking requirements

Before providing S3 storage to clients, you must verify that networking is correctly configured to meet the S3 provisioning requirements.

The following cluster networking objects must be configured:

  • Physical and logical ports
  • Broadcast domains
  • Subnets (if required)
  • IPspaces (as required, in addition to the default IPspace)
  • Failover groups (as required, in addition to the default failover group for each broadcast domain)
  • External firewalls

We will be using a local FabricPool (cloud) tier. To do this, you must also configure intercluster LIFs; cluster peering is not required.

For local FabricPool capacity tiers, you must use the system SVM (called “Cluster”), we will be using data and intercluster LIFs. This option requires additional configuration, including enabling the LIFs for the S3 protocol, but the local tier will also be accessible as a remote FabricPool cloud tier to other clusters.

  1. Display the available physical and virtual ports using DM Series System Manager: Network > Ethernet Ports
    • When possible, you should use the port with the highest speed for the data network.
    • All components in the data network must have the same MTU setting for best performance.
  2. Determine the available Broadcast Domains for each of the network ports: Go to the Storage Manager for DM Series and select Network > Overview > Broadcast Domains.

    Each network port will be listed based on the Broadcast Domain in which the port is located.

  3. Display available IPspaces: Go to the Storage Manager for DM Series and select Network > Overview > IPspaces.
    You can use the default IPspace or a custom IPspace.