Network Native

Often, when helping customers isolate and resolve problems with NSX-V or with HCX ( hybrid cloud extensions ), a redeploy is the best option to fix the problem. When I propose a redeploy, I can sense fear gripping the recipient of the suggestion. I understand the initial fear, because coming from a hardware networking background, I recognize it takes time for NSX-V users to grasp the advantages of software networking over physical networking. Redeploying a hardware router, switch, or firewall is not a small ordeal. You'll need to procure the new device, copy the configuration from old to new, then swing the cabling over from old to new device during a planned maintenance window. With NSX-V, this process happens in a matter of minutes, in an automated fashion, at the literal click of a button. Human error is minimized due to automating the process. For the speed readers, here is the TL;DR of the NSX-V redeploy process: 1. Click Redeploy. 2. vCenter builds out a new VM that lives

The three components of computer infrastructure are considered compute, storage, and networking. When applications don't work properly, its often the case that networking is the first component to receive blame for failed application performance. In the case of virtualized workloads (i.e. applications running on virtual machines), we are fortunate to have a powerful troubleshooting tool which allows us to packet capture network traffic in an ESXi hypervisor. For this blog, I'm going to use an Hands On Lab (HOL) from the VMware website to demonstrate the process of doing a quick live packet capture. The output of the packet capture will be sent to the shell of the hypervisor. There are ways to sent the network traffic to a file so it can be extracted and analyzed by a packet analyzer tool, but that will be for another post. First, lets start with heading over to the HOL website:  https://labs.hol.vmware.com/ For this lab, I'm going to type NSX in the search bar to find

Hello, I'm Daryl. This is my blog. The aim here is to jot down some ideas I have about technology. I'd like to increase my online presence where possible, but at the end of the day I'm only trying to satisfy myself with this blog. Currently, I work in the network virtualization space. If that means nothing to you, maybe this type of tech blog is not your speed. I plan to write about general business computing topics with an emphasis on computer networks. My interest in networking honestly started circa 2000 when I was a sophomore in high school and a buddy told me about an online shooter game allowing 10 versus 10 player matches. At the time, I was skeptical that it was technically feasible to play a video game with more than 4 people at once. Nintendo 64 was the only multiplayer I knew about at the time. I'm not sure if I looked up the game online or not, Internet in the home was still a bit of a novelty back then. I do know that at some point I went to my local Bab