Network Connections

Depending on your desired Network Topology, the following network configuration examples show how to make the physical network connections to support that topology.

NOTE: Later, be sure to make the appropriate port settings that correspond to these network connections.

See Configure the Array Using the Nimble Setup Manager.

One Shared Network

In this configuration:

Management and data paths share the same subnet or network
Any traffic can use any type of port

In the following example, the eth1 port on each controller provides the management path (red cables). The eth4 port on each controller provides the data path (blue cables).

The management and data ports connect to the same network switch. The host also connects to the switch. This is a very simple network, but it still has redundant controllers to provide high availability.

Note that only one management connection and one data connection are shown. You can add more connections and use different ports as needed.

Figure: An example of network connections for one shared network

Two Dedicated Networks

In this configuration:

Management and data paths are on different subnets or networks
Ports eth1 and eth2 handle management traffic
Ports eth3 through eth6 handle data traffic

In the following example, the eth1 port on each controller provides the management path (red cables). The eth4 port on each controller provides the data path (blue cables). The management and data ports connect to different network switches. The host also connects to both switches. The separated management and data paths on this network provide higher performance and high availability.

Note that only one management connection and one data connection are shown. You can add more connections and use different ports as needed.

Figure: An example of network connections for two dedicated networks

Advanced Configuration

In this configuration:

Management and data paths are on different subnets or networks
Port eth1 handles management traffic
Ports eth2 through eth6 handle data traffic

The following example shows one possible way to connect the cabling for an advanced configuration. Note that the subnet addresses in the illustration are just examples. Your settings will differ. The advanced configuration uses the maximum number of data connections on the iSCSI network, to obtain the best availability and throughput.

In more advanced configurations, you can define your own network configuration to handle the desired I/O flow.

Figure: An example of advanced network configuration: data connections

Figure: Topology diagram - advanced network configuration, management connections

Group Configuration

In this configuration:

Management paths for all arrays are on the same subnet
Data paths for all arrays are on the same subnet or subnets
The group of arrays is assembled and managed through the NimbleOS software

The next example shows network connections for arrays that are managed as a group. This example started with a two-dedicated-network configuration, and then added a second array. It does not matter what the management and data connections are, as long as all management paths are on the same subnet and all data paths are on the same subnet. If you have multiple data subnets, be sure that each array has access to all of the data subnets.

Note that you must create the group using the NimbleOS software. You can have up to four arrays in a group.

For instructions on how to create groups, refer to the GUI Administration Guide or the CLI Administration Guide.

Figure: An example of network connections for a group

Dual Fabric Fibre Channel

In this configuration:

Management traffic uses an Ethernet switch
Data traffic uses Fibre Channel switches
Port eth1 handles management traffic
Ports fc1 and fc2 handle Fibre Channel data traffic
The active controller (A or B) receives data traffic from both Fibre Channel switches (dual fabric)

In the following example, the eth1 port on each controller provides the management path (red cables). The fc1 port on both controllers provides the data path from Fibre Channel Switch 1 (green cables). The fc2 port on both controllers provides the data path from Fibre Channel Switch 2 (blue cables). The management ports connect to an Ethernet switch. The host also connects to both Fibre Channel switches. The separated data paths on this network provide higher performance and high availability.

Note that only one management connection and one data connection are shown. You can add more connections and use different ports as needed.

Figure: An example of network connections for dual fabric Fibre Channel