Nutanix: Deploying the Dell XC series

Adventures in deploying the new Dell XC (Nutanix) series systems.  Initial install of a Nutanix based system.

PreRequisites (per XC630 1U system):
  1. 2x 10Gb Ports <-- Trunk Ports
  2. 1x iDrac Port <-- This is for your out of band management.
    • We get these DHCP enabled by default so we can access them the minute their connected.
  3. IPv6 Link-Local Enabled on switch (Recommended/Preferred)
    • Typically enabled by default on modern switches
    • This enables the Nutanix Controller VM's discover each other immediately.
    • You'll need to attach a device physically to that switch
      • Or a VM to that switch to start configuration.
    • This will allow you to setup via a snazzy web interface.
  4. If IPv6 Link-Local is unavailable on the switches, then the setup involves logging into each CVM to perform manual cluster creation.
    • This can be done by logging into each ESXi hosts' shell to ssh into each CVM's local network connection attached to the vSwitchNutanix Interface.
      • This can be done because Nutanix has vmk interface already created on the same local network.
      • Nutanix has an advanced setup doc on their support portal to walk you through the manual cluster creation process.  Although a bit difficult to locate, in my opinion.
    • Log into the controller VM's on each host and assign them an IP address on ESXi's management network so they can discover each other.
Dell will typically ship these out ESXi pre-installed, although Nutanix' Acropolis and Hyper-V are options as well.

In our case, ESXi is currently our preferred hypervisor, so that's what we received.
Front of Dell XC630's

Back of Dell XC630's.  It's a lab, so yeah, it's a mess.  STOP LAUGHING!
Setup is relatively easy assuming you have all the PreReqs in place.  We did not have IPv6 link-local enabled, so setup was a bit more cumbersome than I would have liked.  Once all setup though, this Nutanix system is one sexy beast.

Enabling IPv6 Link Local is highly recommended because, adding new nodes becomes a cake walk.  Prism will automatically detect new ESXi hosts added and introduce them into the cluster.  So if anything to take away, IPv6 link local is a must.

Next, I'll dive into Prism and give my opinion/reflection on that.

Comments

Post a Comment

Popular posts from this blog

NSX-T: vCenter and NSX-T Inventory out of Sync (Hosts in vSphere not showing up in NSX-T)

Image
Summary: NSX-T loses synch w/ vCenter inventory, but statuses don't appear to show an issue.  Basically, you add a host to a vCenter cluster, NSX-T bits should start to automatically installing on new host.  Assuming you've created a Transport Node Profile and associated w/ the cluster.  The problem is that NSX-T doesn't see the new host and its link to the compute manager (vCenter) looks fine. Looks fine, Y U NO WORK!? So what's going on here?  This appears to affect NSX-T 2.5 and 2.5.1.  Cause is unknown. Workaround: Restart the cm-inventory service on each NSX-T mgmt/controller node using API or CLI. Details: If you were to query the status of the cm-inventory via API or CLI, you could query all 3 manager/controller nodes and get a status of running.  Even if the primary node associated w/ the VIP, if configured, is not necessarily in charge of inventory.  So you could restart the cm-inventory service till you are blue in the face and get nowhere be
Read more

MacOS: AnyConnect VPN client was unable to successfully verify the IP forwarding table modifications.

Image
The VPN client was unable to successfully verify the IP forwarding table modification.  A VPN connection will not be established. Summary: I started running into issue utilizing Cisco AnyConnect on my Mac basically complaining about not able to overwrite IP forwarding tables.  This was on 4.6.x.  Since my VPN endpoints were not providing me w/ an updated client and w/ no access to Cisco Anyconnect downloads, my only option was to try openconnect.  It was totally worth it, here is why and how to set it up. PreReqs: Homebrew Installing OpenConnect: Launch MacOS Terminal brew install openconnect Getting VPN IP's/DNS Endpoints from AnyConnect: The information is typically located in your profile xml files located here: /opt/cisco/anyconnect/profile/somethingsomething.xml In the xml file, you are looking for "<HostAddress>typicallyaDNSName.com</HostAddress>" entry.  These are your VPN endpoints that you would need to pass to openconnect. Using
Read more

Azure VMware Solution: NSX-T Active/Active T0 Edges...but

Image
Summary: Azure VMware Solution (AVS) delivers by default w/ a pair of redundant Large NSX-T Edge VM's each running a T0 in active/active mode.  So why is my traffic only going out one Edge VM? Short answer: The default T1 that is delivered w/ AVS is an active/passive T1 where you connect your workloads to.  So while it could technically take either T0, it's always going to go out the closest T0 to the active "SR" T1.  Where do the SR's live?  You guessed it, on the Edge VM's.  As you can imagine, this can lead to a bottleneck if you try to shove all your traffic through a single Edge VM. Simple Diagram: Longer answer with Options:
Read more