Welcome back to my short series on our journey of testing Nutanix and Mellanox. Following up on Part 1 of the Nutanix and Mellanox Series, I’m going to dive deeper into the Nutanix network configuration for use with the Mellanox SX1012.
As I wrote about in the last post that started our journey with Nutanix and Mellanox, we will be testing AHV DR replication for one of our partners while evaluating the use of the Mellanox SX switch platform for a lower cost 10/40Gbe switch.
The NX-1050 Block was pre-configured at another location, so all network subnets will be recreated in this lab. The NX-3050 block is net new, and that will be configured onsite.
This post will serve as the initial setup of the lab testing environment and topology.
I’ve been given the opportunity to do some testing with 2 Nutanix blocks and a Mellanox SX1012 switch for one of our customers, who is looking to do some disruptive changes to the platform they deploy their software onto.
Currently, we partner with this customer to do your typical 3-Tier infrastructure deployments with EMC VNX/VNXe for Storage, Cisco Catalyst and Nexus for switching, Cisco UCS or HP for compute and VMware vSphere for the hypervisor. While this solution has worked very well over the years, when we approached this partner a few years ago with Nutanix, the interest was there but the justification was hard to come by.
Fast forward to this year, we were able to get our partner out to the Nutanix .Next conference for an executive briefing and generate some more internal interest.
To say we were successful is an understatement! By the time we had gotten over our jetlag coming home, it was how fast can we get a POC box onsite to test with. We got a box into their hands, a nice 4 node NX-1050 model, I headed out to California, did the install and gave them the keys and let them start testing – all on Nutanix’s Acropolis Hypervisor (AHV).