Before you install your CS storage systems and deploy a cluster, please plan your cluster topology and network IP assignment based on the requirements of your operating environment.
Factors to Consider
When planning your expected cluster topology, there are several factors to consider, including:
- How many nodes will the cluster contain?
- How many clients will the cluster serve?
- How much storage capacity does the cluster need?
- Does the cluster need additional host boards for data transfer?
Make a Topology Diagram
Make a topology diagram based on your expected topology of the cluster.
As an example, below is a basic topology of a three-node cluster. In this topology, we connect the nodes by using the onboard (“built-in”) host ports.
Choose a Network Combination
Determine which ports will be used as front-end ports and internal ports. Refer to the article below to see all the allowed combinations.
The image below shows all the available network ports on a node controller and the corresponding channel numbers.
In our example, we plan to use only the onboard host ports to form the following network configuration.
- Front-end: Onboard 10GbE x 2 (CH0 + CH1)
- Internal: Onboard 10GbE x 2 (CH2 + CH3)
Prepare Cluster and Network Components
Prepare the following components based on your cluster topology and network combination.
- RJ-45 LAN cables (management)
- Data link cables (front-end and internal)
- Transceivers
- Network switches
- Management PC
- Client with HBA
- Host boards (if needed; must be purchased from Infortrend)
Important!
To make sure you have the compatible components, refer to the Compatibility Guide (QVL) at Support > Technical Support > Scale-out NAS > Downloads.
Based on the same example given above, for a three-node cluster that does not use any host board, we need to prepare the following components.
| Category | Component | Quantity | Remark |
| Cluster side | Cable | 6 | Front-end |
| 6 | Internal LAN | ||
| 3 | Management | ||
| Transceiver | 6 | Front-end | |
| 6 | Internal LAN | ||
| Switch side | 10G switch | 1 | Front-end |
| 10G switch | 1 | Internal LAN | |
| 1G switch | 1 | Management | |
| Transceiver | 6 | Front-end | |
| 6 | Internal LAN | ||
| Server side | PC | 1 | Management |
| Cable | 1 | ||
| Client side | PC | At least 1 | Based on environment requirements |
| HBA | At least 1 | ||
| Cable | At least 1 | ||
| Transceiver | At least 1 |
Prepare Network IP Assignment
Based on your cluster topology and network combination, prepare a network IP assignment table to keep track of the IPs to be used.
For the three-node cluster in our previous example, we will need to assign the following IP addresses.
| Management Network | |
Cluster management IP address *Management port of the master node | e.g. 192.xxx.x.x |
| Front-end Network | |
| Node 1 IP address - Channel 0 | |
| Node 2 IP address - Channel 0 | |
| Node 3 IP address - Channel 0 | |
| Node 1 IP address - Channel 1 | |
| Node 2 IP address - Channel 1 | |
| Node 3 IP address - Channel 1 | |
| Subnet mask | |
| Default gateway | |
| Internal Network | |
| Node 1 IP address - Channel 2 | |
| Node 2 IP address - Channel 2 | |
| Node 3 IP address - Channel 2 | |
| Node 1 IP address - Channel 3 | |
| Node 2 IP address - Channel 3 | |
| Node 3 IP address - Channel 3 | |
| Subnet mask | |
| DNS Server | |
| DNS server IP address | |
Note:
- You can set an IP range for the front-end network if needed.
- You can set an IP range for the internal network if needed.
Home