Book Image

VMware NSX Cookbook

By : Bayu Wibowo, Tony Sangha
Book Image

VMware NSX Cookbook

By: Bayu Wibowo, Tony Sangha

Overview of this book

This book begins with a brief introduction to VMware's NSX for vSphere Network Virtualization solutions and how to deploy and configure NSX components and features such as Logical Switching, Logical Routing, layer 2 bridging and the Edge Services Gateway. Moving on to security, the book shows you how to enable micro-segmentation through NSX Distributed Firewall and Identity Firewall and how to do service insertion via network and guest introspection. After covering all the feature configurations for single-site deployment, the focus then shifts to multi-site setups using Cross-vCenter NSX. Next, the book covers management, backing up and restoring, upgrading, and monitoring using built-in NSX features such as Flow Monitoring, Traceflow, Application Rule Manager, and Endpoint Monitoring. Towards the end, you will explore how to leverage VMware NSX REST API using various tools from Python to VMware vRealize Orchestrator.
Table of Contents (19 chapters)
Title Page
Packt Upsell
Foreword
Contributors
Preface
Index

Configuring VXLAN Networking


The VXLAN VIB is installed as part of the NSX host preparation but it is not ready to use until we configure VXLAN networking. In this recipe, we will prepare a vSphere cluster for VXLAN:

Attributes

Value

vDS

RegionA01-vDS-COMP

VLAN

130

MTU

1,600

VMKNic IP addressing

IP Pool

IP pool details

Name: VTEP_RegionA01-COMP01

Gateway: 192.168.130.1

Prefix Length: 24

Static IP Pool: 192.168.130.51-192.168.130.53

VMKNic teaming policy

Failover

VTEP

1

Getting ready

To configure VXLAN networking, the following prerequisites need to be satisfied:

  • The NSX Manager must be deployed.
  • The NSX controllers must be deployed.
  • The vSphere cluster should be prepared for NSX.
  • The physical network should be configured with a minimum MTU of 1,600 bytes.
  • The physical network should have a VLAN for VTEP VMkernel. In a production environment, VTEP VMkernel network should be in its own unique IP subnet.
  • The physical network ports facing ESXi hosts vmnics should be tagged with VLAN for VTEP VMkernel.
  • The vSphere virtual...