Summary

We started this chapter with an introduction to NSX cross vCenter Server followed by cross vCenter Server components, and universal object creation, and we ended by discussing a few design decisions that we should be well aware of during cross vCenter Server NSX deployment. Way back, network troubleshooting was single-handedly done by network architects and support engineers, which made life easy for vSphere folk. NSX being a network software layer running on top of vSphere, people often believe that it might make their life somewhat threatening since they have a clear visibility on both for both hypervisor and network virtualization layers.

For me, troubleshooting is an art; if we follow a systematic procedure for checking a problem, resolving the problem is a cakewalk. There is no secret or straightforward automation that will help us analyze and fix a problem in network virtualization.

In the next chapter, we will have a detailed discussion on NSX troubleshooting. So let's...