We just learned this week that the PowerEdge VRTX, which was announced in June of 2013, will remain in the Dell EMC portfolio into 2021. This is great news for customers who have invested into the “datacenter in a box” platform and opens up an opportunity for those who aren’t using it. It’s been a while since I’ve talked about the PowerEdge VRTX platform, so here are a few things you may not know. Continue reading →
The past few months have seen some long awaited new additions to Dell’s PowerEdge VRTX system. In an effort to prevent this from being an “all Dell” blog, I’ve held off writing about these new additions until today. In a quick summary, the new additions include: 2nd PERC, added support for VMware ESXi 5.5, added support for the M820 blade server and the ability to repurpose blade servers from the M1000e. Let’s dig into each of these.
As I noted in my original posting of the PowerEdge VRTX, the Chassis Management Controller, or CMC, is available with an “Express” license and an “Enterprise” license. To help you determine which would be best suited for your environment, check out the chart below.
After publishing the details of the PowerEdge VRTX this week, several people stated they would like to know how quiet it is. I could give you the marketing data on how many decibels it runs but instead, I thought I’d put together a short video to show the quietness of PowerEdge VRTX. The video quality is not the best however I think you’ll get the point of how silent PowerEdge VRTX is.
Kevin Houston is the founder and Editor-in-Chief of BladesMadeSimple.com. He has over 15 years of experience in the x86 server marketplace. Since 1997 Kevin has worked at several resellers in the Atlanta area, and has a vast array of competitive x86 server knowledge and certifications as well as an in-depth understanding of VMware and Citrix virtualization. Kevin works for Dell as a Server Sales Engineer covering the Global Enterprise market.
Disclaimer: The views presented in this blog are personal views and may or may not reflect any of the contributors’ employer’s positions. Furthermore, the content is not reviewed, approved or published by any employer.