ALUA setting must be enabled. If ALUA is disabled, the expected I/O performance may not be achieved. In addition, the load on the internode network may increase beyond the expected level, causing delays in non-I/O processing within the VSP One SDS Block or resulting in processing failures.
The following table lists the compute network requirements to set up an FC connection configuration in VSP One SDS Block.
|
Item |
Requirement |
Remarks |
|
|---|---|---|---|
|
Basic configuration |
Configuration with an FC switch is recommended. |
|
|
|
Connectivity |
OS |
The OS of the connected compute nodes must be one supported by VSP One SDS Block. |
|
|
FC access method |
An FCHBA must be used. |
||
|
ALUA setting |
Asymmetric Logical Unit Access (ALUA) of the compute node must be enabled. |
The system might need to be restarted when the ALUA setting is enabled. |
|
|
Bandwidth |
At least 16-Gbps bandwidth is required. |
The recommended bandwidth is 32 Gbps or more. |
|
|
Availability |
When the network is redundant, the convergence time from a failure must be two minutes or less. |
Make the network redundant so that it has no single point of failure (SPOF) that could disable communication in multiple storage nodes. An SPOF could cause a single network appliance failure or other link failure to stop I/O operations for the VSP One SDS Block cluster. |
|
|
Security |
Configure the network to physically or logically isolate it from other networks and prevent unauthorized access. |
||
|
Monitoring |
Configure a network monitoring system (independent of VSP One SDS Block) that detects network failures or performance degradation and enables identification of causes. |
If the monitoring system is not provided, it might be impossible to troubleshoot network failures or performance degradation. |
|
|
Expandability |
Determine a network topology and set the zoning function in consideration of future addition of storage nodes. |
||
|
Network topology |
|
A configuration of two targets per storage node is recommended. |
|
|
Maximum transfer length per I/O request |
The transfer length per I/O request that reaches the volume from the compute node must be 8 MiB or less. |
Typically, the maximum I/O size that reaches the volume can be limited by the settings of the compute node OS, driver, HBA, or hypervisor. Depending on the compute node configuration and settings, I/O requests exceeding 8 MiB might be sent to the volume without being split. In that case, VSP One SDS Block outputs an event log. Follow the instructions in the VSP One SDS Block and SDS Cloud Troubleshooting Reference to resolve the issue. |
|