This section explains how to wire NIC ports on HPE Apollo 4200 Gen9 nodes and how to network a cluster.
The HPE Apollo 4200 Gen9 90T, 180T, and 288T platforms will reach their End of Platform Support (EoPS) on April 20, 2025.
This platform uses a unified networking configuration in which the same NIC handles back-end and front-end traffic. In this configuration, each networking port provides communication with clients and between nodes. You can connect the NIC’s ports to the same switch or to different switches.
To identify the
eth port, run the following command:for i in /sys/class/net/eth*; \
do echo $i; \
cat $i/device/uevent | \
grep -i pci_slot; \
doneNode NICs and Ports
The following diagrams show the NICs and ports on HPE Apollo 4200 Gen9 node types.
288T
Currently, NIC2 on this model is unused.
288T
180T
Currently, NIC2 on this model is unused.
90T
Prerequisites
- A network switch with the following criteria:
- 40 Gbps Ethernet connection
- Fully non-blocking architecture
- IPv6 compatibility
- Compatible network cables
- A sufficient number of ports for connecting all nodes to the same switch fabric
- One static IP for each node, for each defined VLAN
Before you connect any Qumulo-supported equipment to your network, we strongly recommend consulting with your network engineering team.
Recommended Configuration
- Two redundant switches
- One physical connection to each redundant switch, for each node
- One Link Aggregation Control Protocol (LACP) port-channel for each node with the following configuration:
- Active mode
- Slow transmit rate
- Trunk port with a native VLAN
- Enabled IEEE 802.3x flow control (full-duplex mode)
- DNS servers
- Network Time Protocol (NTP) server
- Firewall protocol or ports configured for Qumulo Care Proactive Monitoring
-
Where
Nis the number of nodes, up to 10N-1floating IP addresses for each node, for each client-facing VLANNote
The number of floating IP addresses depends on your workflow and on the clients that connect to the cluster, with a minimum of two floating IP addresses for each node, for each client-facing VLAN, but with no more than ten floating IP addresses for each node, for each client-facing VLAN. - Nodes connected at their maximum Ethernet speed (this ensures advertised performance). To avoid network bottlenecks, Qumulo validates system performance with this configuration by using clients connected at the same link speed and to the same switch as the nodes.
Connecting to Redundant Switches
This section explains how to connect a four-node HPE cluster to dual switches for redundancy. We recommend this configuration for HPE hardware. If either switch becomes inoperative, the cluster remains accessible through the remaining switch.
- Connect the two 40 Gbps ports on the nodes to separate switches.
- Use at least one port on both switches as an uplink to the client network. To ensure an acceptable level of physical network redundancy and to meet the necessary client access throughput rates, use an appropriate combination of 10 Gbps, 25 Gbps, 40 Gbps, or 100 Gbps network uplinks.
- Use at least one peer link between the switches.
Connecting to a Single Switch
This section explains how to connect a four-node HPE cluster to a single switch.
If the switch becomes inoperative, the cluster becomes inaccessible.
- Connect two 40 Gbps ports to the switch.
- Connect any uplink ports to the client network.