Happy New Year! 🙂 In the last two posts we had a look at two different methods for extending VLANs to NSX-T overlay. In the first post we configured a bridge which works well in scenarios where we the source VLAN and destination NSX-T Edge can achieve layer 2 adjacency. In the second post we…
Back in April I published a post about my GitHub repository containing Ansible scripts that perform automated deployment of nested vSphere/NSX-T lab environments. A lot has happened during the last 5 months and now that we’re close to making version 2 the default branch, I thought it would be a good time to give you…
Welcome back! We’re in the process of building an NSX-T Edge – FRRouting environment. In part 1 we prepared the FRR routers by doing he following: Installed two Debian Linux servers Installed VLAN support Enabled packet forwarding Configured network interfaces Installed and configured VRRP Installed FRRouting In this second part we will first deploy the…
Recently a new version of the NSX-T Reference Design Guide was released. This guide, which now covers NSX-T versions 2.0 – 2.5, is a must read for anyone interested in the NSX-T solutions and their recommended design. One of the things you’ll find in the updated guide is a new recommended deployment mode for the…
I recently passed the Professional NSX-T Data Center 2.4 (2V0-41.19) exam and in this short post I would like to share my experience with the exam and some recommendations for preparing for the exam. About the exam As with all VMware exams there is an excellent exam guide available. That guide should be the first…
Read more VMware Professional NSX-T Data Center 2.4 Exam Review
Hi and welcome back. We’re looking into the NSX-T data path and investigating different points at which we can capture network traffic. You may remember from part one that virtual machine “app01” (172.16.2.50) is trying to ping another virtual machine called “web01” (172.16.1.53), but it’s receiving “request timeout”. We’re trying to find out where in the data…
Welcome back! We’re looking at how to gain visibility at different points in the NSX-T data path. You may remember from part one that virtual machine “app01” (172.16.2.50) is trying to ping another virtual machine called “web01” (172.16.1.53), but it’s receiving “request timeout”. We’re trying to find out where in the data path we’re having…
Having good insight into the different components of a network communication path is key when managing networks. This goes for physical networks and for software defined networks. Today I’m having a closer look at the NSX-T data path and more specifically how to capture network traffic at different reference points in the NSX-T data path.…
Anybody working with NSX micro-segmentation knows the importance of monitoring application traffic and the associated distributed firewall rules. Today I just want to share a simple and quick way to increase visibility in the NSX distributed firewall logs. For this short article I’m using NSX-T 2.4.1 and vRealize Log Insight 4.8. vRealize Log Insight has…
One of the first things to configure after deploying the NSX Manager nodes is backup. No NSX-T implementation should ever get configured let alone go live without a working backup (and restore) in place. Let’s have a look at how to set this up. Backup target NSX-T uses SFTP (TCP port 22) to transfer backup…
