BMC network requirements

Basic configuration

• Configure as an L2 or L3 network.

• Configure as a separate physical network with no connectivity to the internode network.

• Can be the same network as the control network.

Configure a physical network that is different from the compute network for performance stability and security improvement.

Connectivity

• The controller node must be able to access the BMC port of any storage node.

• When using the spare node function, the control port of any storage node must be able to access the BMC port of any storage node.

• The BMC ports on all the storage nodes must be able to connect to the NTP server.

• The only requirement is that the route described in the requirement is IP reachable. The communication ports need not be connected to the same subnet.

• Server operations might require access from the BMC port on a storage node to an external server other than the NTP server (such as DNS server and SMTP server) or to the BMC port on another storage node (for example when using iLO federation). For details about these requirements, see the server vendor documentation and configure the network to meet the connectivity requirements.

Bandwidth per node

At least 1-Gbps bandwidth should be available.

Monitoring

Equipped with a network monitoring system independent of VSP One SDS Block to detect network failures and performance degradation (switch failures, link failures, increased delays, increased packet loss, connections at unexpected link speed operating values and duplex operating values, and others), and configure it so that the cause can be identified.

If the internode network is not provided with a monitoring system, it might be impossible to troubleshoot network failures or performance degradation.

Expandability

Determine a network topology and allocate IP addresses that allows for the possibility that storage nodes might be added in the future.