Knowledge about VMware vSphere Nic and IP address planning

First, understand several concepts:1. Differences between ESX and ESXi: vSphere4.x and 5.x
VMware originally stressed the powerful Server Console management mode, that is, ESX, because it is essentially a linux VM concept implemented on hypervisor, you can do a lot of things (many stories that VMware doesn't want to happen ). The SC can be added at will, so there are no restrictions on it. How can we perform redundancy?
 
2. Different VMkernel and SC or hypervisor concepts
SC and hypervisor are essentially local management of ESX or ESXi, and an IP address is sufficient.
VMkernel is a key function of ESX or ESXi. The implementation of these functions requires that your physical links be redundant, or the same subnet segment avoid cross-vlan data problems. They require the same subnet or multi-path as the storage device.
 
3. network resources required for Virtualization
Before planning IP addresses, you must first consider how many physical NICs of ESX or ESXi can be used.
In the vSphere Client Management Interface of VMware, it clearly shows the meaning, which can be divided into three types: a, manage console; B, VMkernel; c, guest VM network
Physical Network Interfaces must achieve physical redundancy on these three networks. This is very simple for VMware, but it is just a problem of your purchase costs.
Once you have enough physical resources, you can achieve multiple functions. Otherwise, what should I do if passthrough is required?
IP address planning is only required for the entire management. We need to consider the Reason for separation. Most of the reasons are the need to isolate network storms and data connections. For example, a storage network absolutely requires the same subnet segment, coupled with multi-path implementation. In addition, the implementation of a separate vlan or physical subnet of VMkernel facilitates the confirmation of some heartbeat packets (the heartbeat data packet capture experiments have been performed for DRS and HA, this packet is vulnerable to errors caused by storm interference)
 
It is recommended that you plan the physical NIC (non-IP) Quantity:
(1) management advice 1 ~ 2 Network Ports
(2) The guest VM network depends on the number of virtual machines you want to implement on this ESX or ESXi and the network bandwidth requirements of these virtual machines. Suggestion 2 ~ 3 Network Ports
(3) when there are many resources for VMkernel, iSCSI is differentiated from the suggestions for Vmotion and HA, and physical redundancy is achieved separately. The specific amount depends on your plan for the Storage Architecture and core functions.
 
 
For four NICs:
First, what are the specific VMS on ESXi? In addition, you do not need to consider which ESXi implements HA or DRS for simple Vmotion and Storage Vmotion.
If you do not want to add a physical Nic, we recommend that you merge SC and VMnetwork as physical network ports (the SC IP address should be in the same vlan as the vCenter ); we recommend that you merge the physical network ports used by VMkernel without considering multi-path. In addition, we recommend that you enable another network port with the same vlan as the ip san on the vCenter machine to facilitate communication.
For IP planning, the vlan segments of the SC and VMnetwork can be considered to be mixed with the physical vlan; the vlan segments of the VMkernel and the vlan segments of the IP-SAN are recommended to be used in new or clean VLANs.
 
 
Attached rules:

Physical NIC (vmnic)	Vswitch (VSwitch)	Port Group (Port Groups)
Vmnic0	VSwitch0	Service Console + VM
Vmnic1	VSwitch0	Service Console + VM
Vmnic2	VSwitch1	VMkernel (ip san) + vMotion
Vmnic3	VSwitch1	VMkernel (ip san) + vMotion

 

Host Name	IP address
ESXI01	10.0.0.120
ESXI01 Vmtion IP	10.0.10.10
ESXI02	10.0.0.121
ESXI02 Vmtion IP	10.0.10.15
ESXI03	10.0.0.123
ESXI03 Vmtion IP	10.0.10.20
Vcenter Server	10.0.0.146

 
This article is from the "My home location" blog