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

Testing connectivity


As we know that our three-tier application, web, app, and DB, is connected to logical switches, let's do some basic testing to confirm their connectivity:

  1. Firstly, go ahead and power on those machines.

  2. Click the vSphere Web Client home icon.

  3. On the vSphere Web Client home tab, click the Inventories | VMs and Templates icon.

  4. Expand the VMs and templates inventory tree and power on each of the following virtual machines found in the discovered virtual machine folder:

    • web-sv-01a

    • web-sv-02a

    • app-sv-01a

    • db-sv-01a

  5. To power on a virtual machine, select the virtual machine in the inventory, then select Power On from the Actions drop-down menu.

  6. Once the machines are powered on, we will go ahead and record their IP address:

    • web-01a: 172.16.10.11

    • web-02a: 172.16.10.12

    • app-01a: 172.16.20.11

    • DB-01a: 172.16.30.11

We now do a simple ping test between web-01a and app-01a as shown in the following screenshot:

Why do we have 100% packet loss when we ping web-01a (172.16.10.11) and app...