May the games begin! Now to remember how to build Ethernet cables. That’s sort of the diametric opposite of Software Defined Networking…
May the games begin! Now to remember how to build Ethernet cables. That’s sort of the diametric opposite of Software Defined Networking…
It’s finally here. The NSX-T Design Guide.
Grab it, read it, become it! This has been published just in time – I’ll be done launching the NSX-V 6.4 classes, and then it’ll be time to dive in to NSX-T. Great stuff!
Ok, so not really. I’ve been thinking about this for a month or two now. I’ve replaced my 2016 MacBook Pro with Touch Bar with, well, a 2013 Mac Pro…and I’m not looking back.
“But John, you travel! How will you work while you’re on the road?” you may be asking. I can’t tell you how much I like my iPad Pro. That’ll be upgraded to a 10.5” shortly – I think that’ll be just right.
Here’s the thing. My job role is changing. Much of that is driven by me. I want to get off the road. I have a new house (and acreage to maintain – that takes time!). My wife and I are raising our grandson. I need to be home more.
Some of it is definitely being driven by the business, too. Education is working on some cool video-based products. And I have most of a studio set up already. It lines up nicely with what I want to be doing.
So if I’m not traveling so much, what am I doing? I’m creating. I’m actually hoping to make this a much more frequent destination for my time. I spent the two months after VMworld kicking out an NSX Micro-Segmentation course. Nothing fancy, but you should go check it out if you haven’t had any NSX training – I think it’s great! Right after we got the first delivery of that out of the way, I made a temporary move to our Curriculum Development team. We’re cranking out new NSX classes, and we’re trying to make ‘em awesome. So there’s a lot of work going into that.
But is that all? Of course not. VMware Learning Zone is a big thing for us right now. You should check that out, too. I’m recording content for that (when time allows). Nothing major right now, but definitely more in the pipeline.
And then, with all of this content creation work I’m doing, I got Scrivener back out, and actually started learning how to use it in earnest. This is one of the greatest things I think I’ve ever found. I can create content until I don’t want to create anymore, and I can do whatever I need to do with it. I think more importantly, it’s helped me start actually organizing thoughts into consumable snippets, and gives me a platform on which to build.
So this has driven me to a change in my daily driver. Earlier this year (once the hype chilled out a bit), I got my hands on a sweet MacBook Pro with Touch Bar. And I _love_ it. I’ve read lots of complaints about the Touch Bar, and whether it’s useful – I hope Apple will be launching a Magic Keyboard with Touch Bar soon. Seriously.
The MBP doesn’t quite fit what I need right now. I bought an OWC Thunderbolt 3 dock to go with it. Which is spectacular. I’ve got my old Thunderbolt Cinema Display rocking out a big screen, and I just picked up a Dell U3417W as a primary display. I do kinda miss the HiDPI joy of Retina displays, but the amount of real estate I have now is unreal, and I’m ok with the tradeoff.
The tradeoff I’m not cool with anymore is the lack of resources for portability. My MBP has 4 hyperthreaded CPU cores, and they’re fast. But they’re not enough for me. I also maxed this thing out at a whopping 16 GB of RAM. Still not enough. Storage, I bumped to a full terabyte, and that’s groovy, but I’ve also got my Synology hanging around in the background for more space if I need it.
With all of this content I’m working through (and the tooling and processes we use), I have a full-time Windows VM I have to run, and I want that to be responsive, so that’s chewing up more than half of my resources right now. And then there’s Camtasia, Logic Pro X, and any other editing tools I need when I’m doing audio or video. And Mail, and Scrivener, and more than one web browser, and whatever else I’m running.
So I took advatage of Other World Computing’s online store (and Black Friday/Cyber Monday), and found a heck of a deal on a trash can Mac Pro, adding another 2 Xeon cores and twice the RAM of the MacBook Pro. Sure, I’m getting what should be considered an old machine, but for what I want to be able to do, it makes a ton more sense. The current Pro certainly doesn’t fit everyone’s use case, but it works great for what I want and need it to do. And I can add memory. Holy crap I miss having that flexibility!
Will I be frustrated late in 2018 when a new Mac Pro is launched? Sure. Am I upset that I’m not waiting another few weeks to get my hands on an iMac Pro? Nah, but that’s an envy-inducing rig right there. I wonder if I can make a business case for my next machine refresh at work………..
Do you know what I’m gonna miss, at least a little bit? Of all things, USB-C. And the Touch Bar, but since I’ve been using the MBP essentially as a desktop, that’s been hidden away from me for a couple of months. But I’m really digging USB-C, for all it’s little gotchas. I like it. And I won’t have any more of it until I refresh this new (old) machine in a while. By then I’m sure we’ll be on a whole new USB spec. And Thunderbolt 4.
Anyway, I’m back to the desktop for a while. I can do everything I need to on the road with my trusty iPad Pro, Pencil, and Smart Keyboard (oh, don’t forget the Spotlight).
What’s out there looking forward? Content. Content on all things NSX. And whatever else I come up with. And I’m going to try to put some here. I’ll see you on the flip side!
Have you ever wondered what log files matter for day-to-day troubleshooting on the NSX Controller nodes? There are certainly a plethora to choose if you just type show log and press ‘Enter’.
If you haven’t looked at the new VMware Documentation site yes, I encourage you to check it out. There’s a whole new layout. Once you get accustomed to it, I think it’s actually easier than the old web-based documentation.
In the Troubleshooting and Operations course, we mention NSX Controller logs a couple of times, and I’d like to expand on that content just a bit.
syslog is, well, the core OS system log. Not entirely unlike any other Linux system. In addition to the standard logging content, however, some HTTP access logs are also included.
Then, there’s the Zookeeper log (
cloudnet/cloudnet\_java-zookeeper<timestamp>.log). This log contains the logged data related to the Zookeeper process that enables NSX Controller Clustering. Some things you may see in this log are disk latency warnings, that could indicate issues with Controller syncing:
Finally, we have the core NSX Controller log file,
cloudnet/cloudnet.nsx-controller.root.log.INFO.<timestamp>. This file contains a wealth of information about the operation of the NSX Controller. Let’s look at some of these messages individually.
What we’re seeing in the above screenshot is an issue with the Controller cluster. Fortunately, it’s very short-lived and does not trigger a control plane issue. The Controller Cluster can’t find any functional nodes, so it announces that the cluster will shut down in 30 seconds. This will trigger all connections to this surviving node to drop, causing a control plane outage. A cluster member, however, joined before the 30 second timer completed. The cluster shutdown is aborted, and the Sharding Manager is invoked to distributed slices to the new cluster member.
The next image simply shows us a VTEP Leave Report being acted upon by the Controller:
Here’s an interesting one:
What we see here is that a host sent a VTEP Join Report to the Controller, but the VTEP was already joined to the VNI. If we look carefully, we see that the existing VTEP Join Report came across Connection ID 7 (
connId=7), while the new, conflicting report came across Connection ID 8. Also worth noting here is that the control plane sync state for the original VTEP Report was good (
isOutOfSync=False), where the new connection has not yet resynchronized its control plane (
And have you ever wondered about hosts sending ARP information for VMs after the VM has been identified? Take a look at this:
There’s a lot to look at when you get into log analysis, but once you can narrow down the important files, interpreting them is actually pretty straightforward.
So I’ve had a few questions about the network in my lab, since I’m teaching almost nothing but NSX these days. So let’s talk about it for a bit.
My network is purposefully simple. And I’ve just rebuilt pretty much everything, so it seems like a good time to document it.
At the edge of my network is a Ubiquiti Networks EdgeRouter Lite (ERL). It deals with all of my routing inside the network, as well as routing to the outside world. It’s a 3 interface device – one to the outside world (cable modem), one to my default VLAN and home network, and the third interface is carved into a bunch of sub-interfaces for my VLANs in the lab.
The two internal-facing interfaces are attached to a Cisco SG300-20 that I could also use for routing, but I chose to let the router deal with that. This is where I have several VLANs set up for my different environments, and that’s all I’ve done with the Cisco switch – no IGMP Snooping, no routing, just VLANs:
Since my lab is completely nested, I also have VSAN and vMotion VLANs configured on my distributed switches, but they don’t map to anything in the physical network.
On the NSX side of things, well, I’m rebuilding that right now. My thought process, since this is a lab, is to attach my outside-facing Edge VMs to the relevant Management network, depending on where I need the Edge. This sort of flies in the face of having a dedicated Edge cluster, but hey, this is a lab 🙂
Inside the Edge, my DLR(s?) will attach to a common Transit network, as will the inside interfaces of the Edges. I’ll set up some OSPF areas so that the EdgeRouter Lite can advertise some networks into the Edge. The DLR will also advertise its routes up to the Edge, which will in turn advertise back to the ERL. This should be a pretty simple OSPF config. I could eliminate the need for OSPF between the Edge and the ERL simply by configuring a default route, but what fun is that?
Then my workloads will attach to whatever Logical Switches I want them attached. The sky’s the limit inside the SDN.
For simplicity’s sake at this point, each network segment (VLAN or VXLAN) will have its own /24, though many of them could make due with a /28 or /29 pretty easily. But I’m not strapped for IP addresses, thanks to our friend RFC 1918, so I’m not going to make things any more complicated than I need to.
Everything works pretty well. Sure, I run into some goofy behavior once in a while (see the VTEP VLAN tagging thing above), but this environment is entirely unsupported. Honestly, it’s a miracle that any of this works at all, and is a galvanizing testament to what VMware software is actually capable of doing.
Someday, maybe I’ll draw this all up. But today is not that day.
Here I am, procrastinating on other stuff, to talk about the new lab setup. I promised in the last video, I’d do a writeup, and I figured “no time like the present”!
So what do I have going on? I’ve ripped out the ML370 and ASUS RS500A boxes, and replaced them with a veritable steal from the Dell Outlet. I decided to go all-in for a nested lab, since I can’t come up with a good reason to put together a physical lab.
So I found a Precision T5610 with a pair of Xeon E5-2620v2s. Twelve hyper threaded cores of processor get up and go. The Scratch and Dent unit I bought had 32 GB of RAM installed, along with a 1 TB spindle. Not a bad start. But I had gear to work with, and needed more RAM.
So I ordered a nice 64 GB upgrade kit from Crucial (well, 4 16 GB kits, technically, hoping it’d give me a 96 GB box to work with. The pre-installed RAM and the Crucial RAM didn’t play too nicely together (Windows wouldn’t load from the spindle, nor would the ESXi installer start). Boo. So I pulled out the factory RAM, ran memtest86 for about a day, just to be safe, and am proceeding, for the moment, with 64 GB.
Still just a start, though, as I needed storage. I had an Icy Dock 4-bay SATA chassis and an IBM M1015 SAS RAID controller in my little HP Microserver. That box didn’t need those things anymore, so a transplant was necessary. 4 screws later, I had lots of room for 2.5” SATA drives. I already had a pair of 120 GB Intel 520 SSDs in Icy Dock trays, and I pulled the 2 1 TB Crucial M550 SSDs from the ASUS box. Now I have plenty of lab storage. If I need more, I can always take the performance hit and attach something from the DS412+ (like I’ve already done with my “ISO_images” NFS share.
**EDIT** I ran into another snag. The LSI controller and Icy Dock combination seem to not be playing nicely with the host. The SSDs seem to randomly just drop offline periodically, which makes me sad. It could be a power thing (these big SSDs are kind of notorious for power problems, especially in small drive chassis or NAS units), but I’m not going to push it any further. I pulled the controller and drive cage out of the system, and I should have a SATA power splitter after UPS shows up today (I was too lazy to leave the house LOL), so I’m just going to run the SSDs off the on-boad SATA controller channels, and be happy about it.
At this point, I thought I was ready for ESXi, but upon installation, I hit a snag. The T5610 has an Intel Gigabit NIC. As such, I expected no issues, but the 82579 isn’t noticed by ESXi 5.5u2 for whatever reason. No biggie – this thing has a nice tool-less case, and less than a minute later, I had a dual-port Intel NIC installed and ready to go (82571EB if you’re curious). One more reboot and ESXi was installing.
Everything’s pretty happy at the moment. Here’s what it looks like now that I’ve built up all my virtual ESXi hosts:
I’ll follow up with some network details shortly, since that’s also gotten _way_ complex recently. All in the name of scenario-based play with NSX. More fun later!
Well, another day, another post.
Ok, that may be exaggerating a bit, but I’m trying. Again. Still.
I’m rebuilding my lab (more to come on that later), and with the big push toward VMware NSX in my life right now, I thought I’d capture my fun and excitement in deploying everything. Here’s Part 1, where I deploy the NSX Manager and register it with vCenter. Nothing earth-shattering here, but it might help someone.