About management network management of ESXi host

On a blog to talk about why to design ESXi host Vmotion Network and Management network separate, weekend in the group encounter an interesting problem, is also about management network, take out and share with you.

As we all know, we usually design a management network to manage ESXi host, have you ever thought of such a scene, a physical server, in the installation of the ESXi 5.0 virtualization software, configure the IP and related parameters to manage the network card, When the vcenter is not installed, we can connect the ESXi host by vsphere client clients, before Vcenter has not configured the network, we can directly add ESXi host to vcenter management interface according to IP, so there is a question:

Management network is used to manage it is not established or deleted it can also be managed is it understandable that you don't need a management network?

Single from our previous practice to see the management network did not play the management function, you are not also confused?

First look at "vsphere Design" in this book is how to describe the management network.

Host networking is divided into the following components:

Service Console (Management Network)

Virtual Machine Port Groups

IP Storage (NFS/ISCSI, FCoE)

VMotion

Fault tolerance

SERVICE CONSOLE
Your Service console/management Network is the lifeline into Your host. If that is lifeline goes down, you can ' t remotely manage that host. The host would-be-would-be-has lost connectivity and may power down all the VMs it has running. The other hosts in the cluster may-your host is down and try to restart the VMs that were running. In a nutshell, bad things happen. You are should never leave your Service Console on a single NIC.

The management network is also called the service Console, is the lifeline of the host, if the lifeline is corrupted, you will not be able to remotely manage (personally think this should be the monitoring) host, the host will think that the virtual machine lost connection, will shut down all the virtual machine running on it, Other hosts will also consider the host as a machine, trying to open a virtual machine that it thought would be lost on other hosts, while the actual virtual machines were still working, in short, an accident occurred. Therefore, we recommend that you configure the management network redundancy to avoid this happening.

So we can draw the following conclusions.

Management traffic-This interface is mainly used to configure the vsphere ha, the management of the network heartbeat transmission, if not checked, means that no vsphere ha no heartbeat network, will be configured to fail;

Other network functions are as follows:

VMotion-This interface is used to support the migration of virtual machines from a ESXi host to the B ESXi host, without which the interface will not migrate;

Fault tolerance-This interface is used to support virtual machine fault tolerance;

IP Storage-This interface is used to connect IP storage, including iSCSI and NFS storage.

I hope you can respond to such an interesting question. Perhaps later directly called Management Network for service console more appropriate.

This article is from the "VirtualBox" blog, please be sure to keep this source http://virtualbox.blog.51cto.com/531002/1004044