Upgrade your Supermicro BIOS firmware from Linux using their SUM utility. 🔧
I’ve talked about predictable network names (and seemingly unpredictable ones) on the blog before, but some readers asked me how they could alter the network naming to fit a particular situation. Oddly enough, my Supermicro 5028D-T4NT has a problem with predictable names and it’s a great example to use here. The problem There’s plenty of detail in my post about the Supermicro 5028D-T4NT, but the basic gist is that something within the firmware is causing the all of the network cards in the server to show up as onboard.
Earlier today, I wrote a post about my first thoughts on the Supermicro 5028D-T4NT server. The 10Gb interfaces on the server came up with the names eth0 and eth1. That wasn’t what I expected. There’s tons of detail on the problem in the blog post as well as the Github issue. Kay Sievers gave a hint about how to adjust the interfacing naming in a more granular way than simply disabling the predictable network names.
I’ve recently moved over to Rackspace’s OpenStack Private Cloud team and the role is full of some great challenges. One of those challenges was figuring out a home lab for testing. The search My first idea was to pick up some lower-power machines that would give me some infrastructure at a low price with a low power bill as well. I found some Dell Optiplex 3020’s on Newegg with Haswell i3’s that came in at a good price point.