Gigabyte H261-Z60 Server Review 2U4N AMD EPYC for Dense Compute

5

Gigabyte H261-Z60 Management Overview

Looking at the Gigabyte H261-Z60 management, we see a departure from the Avocent-based management firmware solution. Instead, Gigabyte is using the HTML5 MegaRAC with a more modern UI. Our Gigabyte H261-Z60 came with the Central Management Controller (CMC) which we are going to discuss in a bit. First, we are going to look at the individual node management.

Gigabyte H261-Z60 Node Management

As one can see, the Gigabyte H261-Z60 utilizes a newer MegaRAC SP-X interface. This interface is a more modern HTML5 UI that performs more like today’s web pages and less like pages from a decade ago. We like this change. Here is the dashboard. One item we will quickly note is that you can see the CMC IP address in the upper left corner that is helpful for navigating through the chassis.

Gigabyte MZ61 HD0 Dashboard
Gigabyte MZ61 HD0 Dashboard

You will find standard BMC IPMI management features here, such as the ability to monitor sensors. Here is an example from one of the machines.

Gigabyte MZ61 HD0 Sensors
Gigabyte MZ61 HD0 Sensors

Other tasks such as the CPU inventory are available. One can see this particular CPU is a new AMD EPYC 7371 high-frequency Naples part that will be available next quarter. We already tested the Gigabyte H261-Z60 with these CPUs.

Gigabyte MZ61 HD0 System Inventory CPU Inventory
Gigabyte MZ61 HD0 System Inventory CPU Inventory

One of the other features is the new HTML5 iKVM for remote management. We think this is a great solution. Some other vendors have implemented iKVM HTML5 clients but did not implement virtual media support in them at the outset. Gigabyte has this functionality and power control support all from a single browser console.

Gigabyte MZ61 HD0 Remote Control IKVM
Gigabyte MZ61 HD0 Remote Control IKVM

We want to emphasize that this is a key differentiation point for Gigabyte. Many large system vendors such as Dell EMC, HPE, and Lenovo charge for iKVM functionality. The feature is an essential tool for remote system administration these days. Gigabyte’s inclusion of the functionality as a standard feature is great for customers who have one less license to worry about.

While each node’s BMC has features for LDAP, AD, RADIUS authentication integration, logging, remote firmware update tools, and similar industry standard functions, what sets the H261-Z60 apart is the CMC which reduces cabling needs in the data center.

Gigabyte H261-Z60 CMC A Big Feature

One of the newer features with this generation is the Gigabyte H261-Z60 CMC. CMC stands for Central Management Controller. This serves two purposes. First, it allows some chassis level features. Second, it allows a single RJ-45 cable to access all four IPMI management ports on the individual chassis which greatly reduces cabling. With 2U 4-node chassis, cabling becomes a big deal. Removing cabling means better cooling efficiency and less spent on cabling, installation, and switch ports. The CMC is an option we wish Gigabyte makes standard on 2U4N designs going forward.

Gigabyte H261 Z60 CMC Port And PSUs
Gigabyte H261 Z60 CMC Port And PSUs

The CMC is run by an ASPEED BMC. This still uses the more traditional Gigabyte management interface, but it has some great features. Here is an example we set up in the lab with a dual CPU node, a single CPU node, a powered off node, and a node removed. An administrator can see this information remotely through one interface per chassis.

Gigabyte H261 Z60 CMC Four Node Modes
Gigabyte H261 Z60 CMC Four Node Modes

The “Node MAC Address” shows information on each node that is physically plugged in. Using the four test cases shown above, we can see that if the node is powered on, we can get the LAN MAC addresses as well as the BMC address/ IPv4/ IPv6 addresses. In a cluster of 2U4N machines, this is important when you need to troubleshoot and find a node.

Gigabyte H261 Z60 CMC Node MAC Address
Gigabyte H261 Z60 CMC Node MAC Address

There are some aggregated sensor data points shared with the CMC for remote monitoring.

Gigabyte H261 Z60 CMC Sensors
Gigabyte H261 Z60 CMC Sensors

You will have to use separate firmware updates for the CMC versus the nodes, that also means there is another BMC to secure and keep updated and the functionality is a bit different between the nodes and the CMC.

Gigabyte H261 Z60 Two Management Interfaces For Firmware Updates
Gigabyte H261 Z60 Two Management Interfaces For Firmware Updates

We like the chassis power figures, the ability to turn the entire chassis off, and the assistance for tying nodes to chassis for inventory purposes. Realistically, the “killer” feature of the CMC is using fewer cables to wire everything. Reducing 4 cables helps mitigate the 2U4N cabling challenge.

Next, we are going to look at performance before moving to power consumption and our final words.

1
2
3
4
5
REVIEW OVERVIEW
Design & Aesthetics
9.7
Performance
9.5
Feature Set
9.4
Value
9.3
Previous articlePutting AWS Graviton and its Arm CPU Performance in Context
Next articleSynology RackStation RS1619xs Plus Launched
Patrick has been running STH since 2009 and covers a wide variety of SME, SMB, and SOHO IT topics. Patrick is a consultant in the technology industry and has worked with numerous large hardware and storage vendors in the Silicon Valley. The goal of STH is simply to help users find some information about server, storage and networking, building blocks. If you have any helpful information please feel free to post on the forums.
gigabyte-h261-z60-server-review-2u4n-amd-epycOur Gigabyte H261-Z60 server review shows how this 2U 4-node AMD EPYC server is targeted at dense compute deployments. We test the server with 256 core and 512 threads to see how it performs versus four 1U servers using fewer cables, using fewer components, and achieving lower power consumption.

5 COMMENTS

  1. Great STH review!

    One thing though – how about linking the graphics to a full size graphics files? it’s really hard to read text inside these images…

  2. My old Dell C6105 burned in fire last May and I hadn’t fired it up for a year or more before that, but I recall using a single patch cable to access the BMC functionality on all 4 nodes. There may be critical differences, but that ancient 2U4N box certainly provided single-cable access to all 4 nodes.

    Other than the benefits of html5 and remote media, what’s the standout benefit of the new CMC?

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.