Book Image

System Center 2016 Virtual Machine Manager Cookbook - Third Edition

By : Roman Levchenko, EDVALDO ALESSANDRO CARDOSO
Book Image

System Center 2016 Virtual Machine Manager Cookbook - Third Edition

By: Roman Levchenko, EDVALDO ALESSANDRO CARDOSO

Overview of this book

Virtual Machine Manager (VMM) 2016 is part of the System Center suite to configure and manage datacenters and offers a unified management experience on-premises and Azure cloud. This book will be your best companion for day-to-day virtualization needs within your organization, as it takes you through a series of recipes to simplify and plan a highly scalable and available virtual infrastructure. You will learn the deployment tips, techniques, and solutions designed to show users how to improve VMM 2016 in a real-world scenario. The chapters are divided in a way that will allow you to implement the VMM 2016 and additional solutions required to effectively manage and monitor your fabrics and clouds. We will cover the most important new features in VMM 2016 across networking, storage, and compute, including brand new Guarded Fabric, Shielded VMs and Storage Spaces Direct. The recipes in the book provide step-by-step instructions giving you the simplest way to dive into VMM fabric concepts, private cloud, and integration with external solutions such as VMware, Operations Manager, and the Windows Azure Pack. By the end of this book, you will be armed with the knowledge you require to start designing and implementing virtual infrastructures in VMM 2016.
Table of Contents (16 chapters)
Title Page
Packt Upsell
Contributors
Preface
Index

Networking – Configuring VM Networks and Gateways


A VM network exists on top of a logical network, enabling you to create multiple virtualization networks to isolate and abstract the virtual machines from the logical networks. The types of VM networks in VMM 2016 are as follows:

  • Isolation (network virtualization):
    • Without the VLAN constraints, isolation enables VM deployment flexibility as the VM keeps its IP address independent of the host it is placed on, removing the necessity for physical IP subnet hierarchies or VLANs.
    • It allows you to configure numerous virtual network infrastructures (they can even have the same customer IP address (CA)) that are connected to the same physical network. A likely scenario is either a hosting environment, with customers sharing the same physical fabric infrastructure, or an enterprise environment with different teams that have different objectives also sharing the same physical fabric infrastructure or even on a software house having test, stage, and production...