Book Image

VMware NSX Network Essentials

By : sreejith c
Book Image

VMware NSX Network Essentials

By: sreejith c

Overview of this book

VMware NSX is at the forefront of the software-defined networking revolution. It makes it even easier for organizations to unlock the full benefits of a software-defined data center – scalability, flexibility – while adding in vital security and automation features to keep any sysadmin happy. Software alone won’t power your business – with NSX you can use it more effectively than ever before, optimizing your resources and reducing costs. Getting started should be easy – this guide makes sure it is. It takes you through the core components of NSX, demonstrating how to set it up, customize it within your current network architecture. You’ll learn the principles of effective design, as well as some things you may need to take into consideration when you’re creating your virtual networks. We’ll also show you how to construct and maintain virtual networks, and how to deal with any tricky situations and failures. By the end, you’ll be confident you can deliver, scale and secure an exemplary virtualized network with NSX.
Table of Contents (15 chapters)
VMware NSX Network Essentials
Credits
Foreword
About the Author
About the Reviewer
www.PacktPub.com
Preface

Universal segment ID


The universal segment ID pool is used to assign VNIs to universal logical switches, to ensure that we don't use the same segment ID pool for local and global logical switches; there would be overlapping segment IDs in that eventually.

The following figure shows Universal Segment ID pool creation:

The whole purpose of creating universal logical switches is to span the logical network across vCenter sites without doing traditional complex routing and switching. That way, universal logical switches will be available on all the vCenter Servers in the cross domain NSX site and we can simply connect virtual machines to those logical switches. The virtual machine logical switches will always remain as port groups and NSX will take care of cross vCenter switching. Haven't we configured a more simplified Layer 2 switching than this? First of all, was it possible do a Layer 2 switching like this in the past? I strongly believe we have all already moved away from legacy network...