vmware

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…

Read more Single N-VDS per Edge VM

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…

Read more Installing NSX Intelligence

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…

Read more NSX-T Recoverability – Part 1

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…

Read more NSX-T Data Path Visibility – Part 3

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…

Read more NSX DFW Quick Tip: Tag and Trace

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:…

Read more Getting Started with the NSX-T API and Postman