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…
With NSX-T 2.5 comes NSX Intelligence 1.0. This component, which is part of NSX Data Center Enterprise Plus, is something I’ve been looking forward to since it was announced. NSX Intelligence adds a powerful analytics engine to the NSX-T platform. It provides workload and network context that is unique to NSX. Application owners and operations…
Like everything else in life, stuff can break in your NSX-T environment too. When that happens it’s important to understand how to get things back on track again. In the following blog articles I’m going through a couple of NSX-T failure scenarios and look at how to recover from them. As usual I’m doing this…
On August 30th 2019 I passed the brand new VMware Advanced Design NSX-T Data Center 2.4 exam. Let me tell you a little more about this exam and how I prepared for it. About the exam As far as I know 3V0-41.19 is the first ever design exam within the network virtualization certification track. A…
Read more VMware Advanced Design NSX-T Data Center 2.4 Exam Review
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…
UPDATE 01/10/2019: As pointed out in the comments importing the NSX-T OpenAPI specification into Postman doesn’t work anymore. This is due to NSX-T OpenAPI specification not being totally compliant with the OpenAPI specification and Postman becoming less forgiving about this in newer versions. A workaround is to fetch the NSX-T OpenAPI specification in YAML format:…
