Tag Archives: Nsx

Learning VMWare NSX – VCP6-NV

It is always amazing to hear from my readers any feedback about the book. Today I heard from a Senior Engineer that he passed the VCP6-NV and that the Learning VMware NSX book series was of great help. This is great to hear, as an author, I feel more motivated to write more and help each other.



What goes on on the VSAN Network? Let’s take a brief look at that so we can understand the different types of chatter that goes on this network.

First things first, there is the communication that takes place between all the hosts participating in a vSAN cluster. A heartbeat is sent from the master node to all the other nodes participating in a vSAN cluster. Since vSAN 6.6, this communication is done via unicast traffic.

When a host is part of the vSAN cluster, it can get one of the three roles – master, agent, and backup. As an admin, you have no control over who you can pick as a master vs a backup and this is completely handled by vSAN. This is the second type of communication that happens between the hypervisors participating in a vSAN cluster. The master node is responsible for getting the clustering, monitoring, membership and directory services updates to all nodes (CMMDS).  This traffic is unicast since vSAN 6. The volume of traffic between the master, agent, and backup is light and in steady state, so high bandwidth is not of a concern.

The majority of traffic on a vSAN network comes from the virtual machine disk I/O. VMs on the vSAN datastore is made up of a set of objects which are made up of one or more components. When a VM has multiple copies, it will have its replicas traverse the vSAN network on to other nodes. This is unicast traffic and forms the majority of the vSAN network traffic.

Best practice for the vSAN network is to have a minimum of 10Gb and no routing. If the traffic needs to be routed, then only use static routes in the environment but it is not recommended. Also do not put vSAN traffic on an overlay NSX network, because of circular dependency, this configuration is NOT supported.


An interesting question, if VSAN networking can be done/configured on VXLANS backed by NSX?

The answer is No and this is to avoid a circular dependency.

“However, very often, the question of compatibility is asked in the context of being able to place the vSAN network traffic on an NSX managed VxLAN/Geneve overlay. In this case, the answer is no, NSX does not support the configuration of the vSAN data network traffic over an NSX managed VxLAN/Geneve overlay. This is not unique to vSAN. The same restriction applies to any statically defined VMkernel interface traffic such as vMotion, iSCSI, NFS, FCoE, Management, etc.

Part of the reason for not supporting VMkernel traffic over the NSX managed VxLAN overlay is primarily to avoid any circular dependency of having the VMkernel infrastructure networks dependent on the VxLAN overlay that they support. The logical networks that are delivered in conjunction with the NSX managed VxLAN overlay are designed to be used by virtual machines which require network mobility and flexibility.”

Now you know..


VMworld 2017 is close and the vExpert team made sure they kept us happy.

Today I got my vExpert NSX VMworld Swag! A big box of goodies that helps vExperts stand out in the crowd.

Have a look

Inside there is a Jacket, a T-shirt and a water bottle – all branded vExpert NSX 2017!

Sweet – Thanks NSX vExpert Team!

New NSX Versions

VMware today announced new NSX versions

New NSX Offerings

Standard Edition: Automates IT workflows, bringing agility to the data center network and reducing network operating costs and complexity.

Advanced Edition: Standard Edition plus a fundamentally more secure data center with micro-segmentation. Helps secure the data center to the highest levels, while automating IT provisioning of security.

Enterprise Edition: Advanced Edition plus networking and security across multiple domains. Enables the data center network to extend across multiple sites and connect to high-throughput physical workloads.

See more at: http://www.vmware.com/products/nsx/compare.html#sthash.Cd9wHe5e.dpuf

Learning VMware NSX – The Book!

Learning VMware NSX, Ranjit Singh Thakurratan, eBook - Amazon.com 2016-01-31 23-27-52My first book about deploying and using VMware’s NSX network virtualization platform is out for pre-order. It was indeed a challenge to write a book.

I spent most of last year writing the book and its finally all set to release soon. It has been an interesting but tough journey and writing the book wasn’t easy at all!  Adding to the challenge was the fact that the publisher wanted to keep the book to less than 200 pages. That however was a blessing in disguise, more readers will be willing to read a quick 200 page book about NSX rather than a 600 page gorilla.

The book is available on Amazon and is published through Packt Publishing. The kindle version is available now with the paperback shipping in early March.


Below are some highlights about the book,


To know more about me click here.

Teaser – Learning VMware NSX – Virtxpert Repost

I have been working on my book for a while now and have picked two of the best reviewers to keep me honest. The book is about VMware NSX and is the only NSX book as far as I am aware(that isn’t focussed on certification only). 

The book is now available for pre order and below is what Jonathan from www.virtxpert.com has posted. Enjoy the read.

I have been fortuneate enough in my day job to get hands on experience with VMware NSX, even before the bits were available to download I was supporting NSX via the Federation Enterprise Hybrid Cloud, as it is one of the core components. For people still looking to get a jump start on learning NSX, I wanted to give you a bit of a teaser for an upcoming book by Ranjit Singh – Learning VMware NSX.


Since I am a technical reviewer for this book, which is being published by Packt Publishing, I can’t give away to much but can tell you it is packed with step by step examples on how to get up and running quickly with NSX and understand the various components and how they interact. Keep an eye out on the Packt site, and I expect you’ll here more from me and @rjapproves when it is released!

VMware NSX Session at Atlanta VMUG UserCon Today! 

For anyone in and around Atlanta, make sure you make it to GWCC convention center for the VMUG UserCon 2015!

Atlanta has one of the busiest VMUG and I will be presenting on getting started with VMware NSX!

You can also meet up with Mariano Maluf – the president of VMUG and other big wigs as well.

Also get to meet Kelley O’Hara – from the national football team and am hoping to take a picture with her. She’s awesome!

See you there! 


Redoing my home lab is always fun, but its a lot more fun when NSX comes into the mix. It all started with this customer who wanted NSX so bad.. well here I am trying to find out why?

Let me be honest, I am NOT a networking guru. It has almost always been one giving me headaches but NSX feels so refreshing and easy enough to wrap my head around it.

So heres a quick refresher for two most important components – I don’t talk about all the components here, only a few for now but more on their way.

1. Segment IDS – Segment IDs, as Wahl rightly puts it, are like VLANs for you VXLAN. Imagine having multiple NSX Management servers talking to a single vcenter, their traffic will be separated by the segment ids – is one use case. Now for each VXLAN virtual wire you get one segment ID assigned to it. So how many segment IDS are allowed? 16 billion! Yes 16 billion of them. So that we don’t get confused with the physical VLAN ids – the segment ids start with 5000. Now I created 5 Segment IDS from 5000 to 5005. Also remember this is a system wide setting!


2. Transport Zone – Transport zones are basically Network scopes in VCNS, if you recall what they are. Let me explain, when you create a transport zone you add a cluster to it. This basically defines the scope of that VXLAN virtual wire. If you have 5 clusters that need to be able to access the same VXLAN virtual wires then they need to be part of the same Transport Zone.

3. Logical Switches – Logical switches are virtual wires – basically VXLANs. When you create a logical switch you assign it to a transport zone. This allows all clusters that belong to the same transport zone to be now configured/exposed to that logical switch. This allows VM’s in a cluster to be able to talk to each other on this VXLAN logical wire without having to create a physical vlan. Remember once a logical switch is created you cannot change its transport zone. You will have to remove it and recreate it to change its transport zone.


More to come keep you posted 🙂