vsphere Deployment family of 07--vcenter management ESXi hosts

vsphere Deployment family of 07--vcenter management ESXi hosts

In the previous post section, the ESXI-MGT, esxi01, esxi02 three ESXi physical hosts are installed, and the vcenter environment is deployed in the virtual machines in the ESXI-MGT (10.1.241.20) host. The next thing to do is to add esxi01 (10.1.241.21), esxi02 (10.1.241.22) two hosts to vcenter to accept vcenter management.

For the overall planning of the experimental environment, please see the previous blog post, "Vsphere Deployment series of 03--experimental environment master plan".

650) this.width=650; "Src=" Http://s3.51cto.com/wyfs02/M00/84/97/wKiom1eVsqrSWNLRAALXJy2rt0w273.png-wh_500x0-wm_3 -wmp_4-s_3018640108.png "title=" network topology figure 02.png "alt=" Wkiom1evsqrswnlraalxjy2rt0w273.png-wh_50 "/>

▲ Master plan network topology diagram

First, pre-work

The first time you log in to vcenter, you need to create a datacenter before you can add hosts and perform subsequent operations. For the purposes of usage, this article is done in the vsphere client.

Use vsphere client to connect to Vcenter, select the vcenter server name (sqvcenter.sqing.local) in the left-hand box, select the New Datacenter submenu in the menu that pops up, or click Create Data center on the Getting Started page Link

In this case, create a data center called "Sq-datacenter".

650) this.width=650; "Src=" Http://s5.51cto.com/wyfs02/M02/84/97/wKiom1eVszKSSG7_AAHbVxm65yc737.png-wh_500x0-wm_3 -wmp_4-s_3101703653.png "title=" 01.png "alt=" Wkiom1evszkssg7_aahbvxm65yc737.png-wh_50 "/>

▲ New data Center in "sqvcenter.sqing.local"

650) this.width=650; "Src=" Http://s1.51cto.com/wyfs02/M02/84/97/wKioL1eVsz6Q8r7VAAISc2oAeQY815.png-wh_500x0-wm_3 -wmp_4-s_2226186538.png "title=" 02.png "alt=" Wkiol1evsz6q8r7vaaisc2oaeqy815.png-wh_50 "/>

▲ Adding a host to a data center named "Sq-datacenter"

Second, add the host

Adding a host is a simple operation, in the Add Host Wizard, enter the ESXi host IP and Administrator account number, password, is basically the next step in the line. Not detailed.

650) this.width=650; "Src=" Http://s1.51cto.com/wyfs02/M00/84/97/wKiom1eVs2XCVT2FAADOdVyCpvU247.png-wh_500x0-wm_3 -wmp_4-s_337316298.png "title=" 03.png "alt=" Wkiom1evs2xcvt2faadodvycpvu247.png-wh_50 "/>

▲ The first step, enter the host IP, user name and password

Next, you assign a license to the host, set the lockdown mode, and the location of the virtual machine.

Licenses are licensed using Vcenter, and other settings are default.

650) this.width=650; "Src=" Http://s2.51cto.com/wyfs02/M02/84/97/wKioL1eVs7HDQ5C2AADPuN7XMs4238.png-wh_500x0-wm_3 -wmp_4-s_3101426414.png "title=" 09.png "alt=" Wkiol1evs7hdq5c2aadpun7xms4238.png-wh_50 "/>

▲ The last step, display the configuration content

At this point, the host is added, and the other hosts are added in the same way.

Third, the alarm processing

1. Hardware Alarm

In the left box host list, if the host icon has a red exclamation point, it generally indicates that the host has a hardware failure. On the Alerts page, you can view specific alert content. You can also click the Alerts tab at the bottom of the main interface, and in the expanded built-in box, you can also view the contents of the alert (click again to shrink back).

In this case, ESXI01 and esxi02 two hosts are equipped with two power supply, but only one power supply, not affect the use, but this appears to be a problem in the vcenter, Alarm, alarm content "host hardware power state." This alert can be cleared, and the red exclamation mark disappears when cleared.

In the production environment, if there are alarms such as CPU or memory, they should be processed in time.

650) this.width=650; "Src=" Http://s5.51cto.com/wyfs02/M00/84/97/wKioL1eVs-TyH17MAAFgk3JjLUU026.png-wh_500x0-wm_3 -wmp_4-s_564641472.png "title=" 21.png "alt=" Wkiol1evs-tyh17maafgk3jjluu026.png-wh_50 "/>

▲ "Sq-datacenter" is selected here, which lists the alarms that exist in all the hosts it includes, which can be cleared.

2. System alert

In the left box host list, if the host icon with a yellow exclamation point, generally indicates that the host has a system failure or other hidden trouble. This is not necessarily prompted on the Alerts page.

In this case, there is a yellow exclamation point, because the ESXi host opened SSH, which is a security risk, in the "Summary" page with special hints.

650) this.width=650; "Src=" Http://s4.51cto.com/wyfs02/M01/84/97/wKiom1eVtAKw2CrvAAF-RMHwaLY362.png-wh_500x0-wm_3 -wmp_4-s_1047986680.png "title=" 11.png "alt=" wkiom1evtakw2crvaaf-rmhwaly362.png-wh_50 "/>650) this.width=650;" Src= "http://s2.51cto.com/wyfs02/M01/84/97/wKioL1eVtBvityJzAAF-_0Lr6Iw231.png-wh_500x0-wm_3-wmp_4-s_2051760902. PNG "title=" 22.png "alt=" Wkiol1evtbvityjzaaf-_0lr6iw231.png-wh_50 "/>

▲ Enable SSH-raised yellow exclamation warning

Four, time configuration

In a virtualized environment, it is important that the time and vcenter of each ESXi host be consistent, so that NTP servers and NTP clients are built to achieve time synchronization.

1. NTP server configuration (non-vcenter operation)

In this case, use the Domain control server (virtual machine sqdc01,10.1.241.11) as the time server.

In a production environment, it is generally not recommended to configure the time server in the domain control, because in practice it will be found that ESXi is difficult to synchronize with the server, usually over the last day (perhaps a half day, do not know when the night) to achieve time synchronization. However, this problem can be solved by modifying the ESXi configuration, which is slightly more complicated.

In Windows Server R2 to configure NTP, mainly by repairing the registry to achieve, online data more, here is not in detail, it is important to note that in the case of a firewall, be sure to open the UPD 123 port.

2. NTP Client Configuration

The NTP client here refers to the NTP client that is built into ESXi. The default is no configuration, no boot.

This configuration can be set in SSH remote, using commands, or in the "Time Configuration" of vcenter, a vsphere client connection. The latter is more intuitive and uses the latter.

In the main interface, select the host that you want to configure, and then switch to the time configuration option, configuration page. You can see that the NPS client is in the stopped state at this time. Clicking the properties link in the upper right will bring up the time Configuration Properties dialog box.

650) this.width=650; "Src=" Http://s4.51cto.com/wyfs02/M01/84/97/wKioL1eVtH-g-VjHAAFGq72cC_A004.png-wh_500x0-wm_3 -wmp_4-s_2974478824.png "title=" 01-copy. png "alt=" wkiol1evth-g-vjhaafgq72cc_a004.png-wh_50 "/>

▲ Time Configuration Interface

650) this.width=650; "Src=" Http://s5.51cto.com/wyfs02/M02/84/97/wKioL1eVtJGxAFORAACXg8vCdXE860.png-wh_500x0-wm_3 -wmp_4-s_951741389.png "title=" 02.png "alt=" Wkiol1evtjgxaforaacxg8vcdxe860.png-wh_50 "/>

▲ The Time Configuration Properties dialog box, where you first tick "NTP client Enabled" and then click the "Options" button, the "NTP Daemon Options" dialog box pops up.

650) this.width=650; "Src=" Http://s2.51cto.com/wyfs02/M00/84/97/wKiom1eVtKzzJ7leAAB_h5VW7PM971.png-wh_500x0-wm_3 -wmp_4-s_1207453409.png "title=" 03.png "alt=" Wkiom1evtkzzj7leaab_h5vw7pm971.png-wh_50 "/>

▲NTP Daemon Options dialog box, in NTP settings, add the NTP server,

Add 10.1.241.11 here (domain-controlled virtual machine with NTP server)

650) this.width=650; "Src=" Http://s1.51cto.com/wyfs02/M01/84/97/wKiom1eVtLqzAPoQAABo5IdCfYw991.png-wh_500x0-wm_3 -wmp_4-s_2257668337.png "title=" 04.png "alt=" Wkiom1evtlqzapoqaabo5idcfyw991.png-wh_50 "/>

▲NTP The Daemon Options dialog box, in general, select the start and stop with host policy, and then start the NTP service with the Start button. Click OK to close the dialog box and return to the Time Configuration dialog box.

At this point, the NTP configuration is complete.

3. NTP optimization

In response to the previously mentioned problem of long synchronization time, online Daniel Wang Chunhai teacher has introduced the solution, as follows:

1), connect to ESXi host via SSH client

2), use VI Editor, modify/etc/ntp.conf, add a line on the last line:

TOS Maxdist 30

3), using the VI editor, modify the/etc/likewise/lsassd.conf file, remove the note in the # sync-system-time = no front, and set its value to Yes:

Sync-system-time = yes

4) Execute./ETC/INIT.D/LSASSD Restart, restart LSASSD service

5) Execute./ETC/INIT.D/NTPD Restart, restart NTPD service

In practice, the ESXi host can synchronize time with the NTP server in the domain in more than 10 minutes after the above setup. (Is there a parameter to set the time interval for synchronization?) Not found)

Five, network configuration

1. vsphere Standard Switch architecture

The first step is to understand the concepts of vsphere standard switches, virtual machine port groups, and the Vmkernel TCP/IP network layer.

In ESXi, you can create two abstract network devices, the vsphere standard switch and the vsphere distributed switch. The distributed switch is specialized in the future, and the vsphere standard switch is used in this case. The vsphere Standard switch operates in much the same way as a physical Ethernet switch, which bridges internal traffic between virtual machines in the same VLAN and links to external networks.

650) this.width=650; "Src=" Http://s2.51cto.com/wyfs02/M02/84/97/wKiom1eVtTajcmJdAAG5S3jilDg655.png-wh_500x0-wm_3 -wmp_4-s_2521464219.png "title=" vSphere standard switch architecture. png "alt=" wkiom1evttajcmjdaag5s3jildg655.png-wh_50 "/>

▲vsphere Standard switch architecture (from official sources)

The vsphere standard switch provides two types of network services to ESXi hosts: the virtual machine Port group and the Vmkernel TCP/IP network layer.

A Virtual Machine Port Group: Connect the virtual machine to the physical network and the virtual machine, and specify port configuration options such as bandwidth throttling and VLAN tagging policies for each member port.

B VMkernel TCP/IP network layer: Connect VMkernel services (such as Vmotion, NFS, ISCSI, and host management) to the physical network.

2. Configuration of vsphere Standard switches

In the main interface, configure, network, you can view and configure the vsphere standard switch.

650) this.width=650; "Src=" Http://s2.51cto.com/wyfs02/M00/84/97/wKiom1eVtV3RZm6zAAFoBIe3Rzg250.png-wh_500x0-wm_3 -wmp_4-s_226962431.png "title=" 00-copy. png "alt=" wkiom1evtv3rzm6zaafobie3rzg250.png-wh_50 "/>

After the ▲ESXI system is loaded, the network is initially configured, where

Management Network is the management of networks, using the Vmkernel port group;

VM Network, the default is the network used for the virtual machine, using the virtual machine port group.

Click "Add Network" in the outer "network" column to create a new vsphere standard switch and configure the port;

You can edit the VSwitch0 port by clicking Properties in the inner layer standard switch: vSwitch0.

The next step is the specific configuration of the vsphere standard switch, which is a critical and complex one.

Note: In this case, the four NICs of each server are connected to the trunk port of the physical switch, and the trunk port allows all VLANs to pass through.

1) Configuration VSwitch0

In this case design, VSwith0 connects Vmnic0 for managing networks and virtual machine networks. Where the management network uses VLAN 241, the virtual machine uses VLAN240, 2,412 network segments.

Virtual network	Properties	vsphere Standard Switches	Connecting to a physical network card	Allow VLAN
Management Network	Vmkernel Port Group	VSwitch0	Vmnic0	Vlan 241
VLAN241	Virtual Machine Port Group	VSwitch0	Vmnic0	Vlan 241
VLAN240	Virtual Machine Port Group	VSwitch0	Vmnic0	Vlan 240

Now it's time to rename the current virtual machine Port Group "VM Network" to "VLAN241" and label its network tag "VLAN241", which allows VLAN241 traffic to pass.

Additionally, add a virtual machine port group "VLAN240" and note its network label as "VLAN240" to allow VLAN240 traffic to pass.

In the network configuration, clicking Properties in the Inner standard switch: VSwitch0 will pop up the VSwitch0 Properties dialog box to edit the VSwitch0 port.

650) this.width=650; "Src=" Http://s3.51cto.com/wyfs02/M00/84/97/wKioL1eVtmLy1CvmAABwqtu9H6g385.png-wh_500x0-wm_3 -wmp_4-s_4125587779.png "title=" 01.png "alt=" Wkiol1evtmly1cvmaabwqtu9h6g385.png-wh_50 "/>

▲vswitch0 Properties dialog box

In the list box, select VM Network, and then click the Edit button to bring up the VM Network Properties dialog box.

650) this.width=650; "Src=" Http://s1.51cto.com/wyfs02/M00/84/97/wKiom1eVtnPzqBwpAAA1hxH0kZU037.png-wh_500x0-wm_3 -wmp_4-s_3476959353.png "title=" 02.png "alt=" Wkiom1evtnpzqbwpaaa1hxh0kzu037.png-wh_50 "/>

▲VM Network Properties dialog box

This changes the network label from "VM Network" to "VLAN241";

In the VLAN ID, enter the VLAN ID number that allows traffic to pass, and here is "241".

When the operation is complete, click OK to close the dialog box and return to the previous Level dialog box.

The modification is complete, and the next step is to create a new virtual machine port group that allows VLAN 240 traffic.

650) this.width=650; "Src=" Http://s5.51cto.com/wyfs02/M00/84/97/wKiom1eVtoajm4gZAABqYHhGW2I534.png-wh_500x0-wm_3 -wmp_4-s_3875707808.png "title=" 03.png "alt=" Wkiom1evtoajm4gzaabqyhhgw2i534.png-wh_50 "/>

▲vswitch0 The Properties dialog box, click the Add button and the Add Network Wizard dialog box will appear.

650) this.width=650; "Src=" Http://s5.51cto.com/wyfs02/M00/84/97/wKioL1eVtpbxvUe7AABK3btDm7k998.png-wh_500x0-wm_3 -wmp_4-s_3682006457.png "title=" 04.png "alt=" Wkiol1evtpbxvue7aabk3btdm7k998.png-wh_50 "/>

▲ Add Network Wizard dialog box, select "Virtual Machine", then next

650) this.width=650; "Src=" Http://s5.51cto.com/wyfs02/M01/84/97/wKiom1eVtqfjrolUAABsbmUe5e8085.png-wh_500x0-wm_3 -wmp_4-s_3539280047.png "title=" 05.png "alt=" Wkiom1evtqfjroluaabsbmue5e8085.png-wh_50 "/>

▲ Add Network Wizard dialog box, set the network label as "VLAN240", VLAN ID "240", and then complete the next step. Returns to the previous Level dialog box.

650) this.width=650; "Src=" Http://s1.51cto.com/wyfs02/M01/84/97/wKiom1eVtuLSjRr-AAB0LpqT80g945.png-wh_500x0-wm_3 -wmp_4-s_1331626535.png "style=" Float:none; "title=" 06.png "alt=" Wkiom1evtulsjrr-aab0lpqt80g945.png-wh_50 "/>

650) this.width=650; "Src=" Http://s1.51cto.com/wyfs02/M00/84/97/wKiom1eVtuKTee0iAAB5HXdEjeA202.png-wh_500x0-wm_3 -wmp_4-s_3850810069.png "style=" Float:none; "title=" 07-copy. png "alt=" wkiom1evtuktee0iaab5hxdejea202.png-wh_50 "/ >

▲ viewing vSwitch0 changes in the primary network configuration

2) Add Network

In this case design, three additional network vmotion, backup and iSCSI are required for virtual machine migration, data backup, and connection of IP SAN storage. Each of the three networks corresponds to a separate vsphere standard switch, and three vsphere standard switches each correspond to a separate NIC.

		vsphere standard switch	Connect to physical network card	allow VLAN
vmotion	vmkernel Port Group	vswitch1	vmnic1	vlan 242
backup	vmkernel Port group	vswitch2	vmnic2	vlan 243
ISCSI	vmkernel Port Group	vswitch3	vmnic3	vlan 244

In the network configuration, click Add Network in the Outer Network column, and the Add Network Wizard dialog box pops up to create a new vsphere standard switch and configure the port.

The following is an example of creating a Vmotion network, which describes how to create a Vmkernel port group network.

650) this.width=650; "Src=" Http://s4.51cto.com/wyfs02/M02/84/98/wKioL1eVt7OBtAxKAABIsepin1U962.png-wh_500x0-wm_3 -wmp_4-s_1003035919.png "title=" 08.png "alt=" Wkiol1evt7obtaxkaabisepin1u962.png-wh_50 "/>

▲ Select Vmkernel

650) this.width=650; "Src=" Http://s4.51cto.com/wyfs02/M00/84/97/wKiom1eVt8Tj9SEQAACTX8YpWnE947.png-wh_500x0-wm_3 -wmp_4-s_37700256.png "title=" 09.png "alt=" Wkiom1evt8tj9seqaactx8ypwne947.png-wh_50 "/>

▲ to create a vsphere standard switch (instead of using an existing vSwitch0), select Vmnic1 as its corresponding physical NIC.

650) this.width=650; "Src=" Http://s2.51cto.com/wyfs02/M01/84/97/wKiom1eVt-zSnR7qAABgd_-TJUI406.png-wh_500x0-wm_3 -wmp_4-s_3084101490.png "title=" 10.png "alt=" Wkiom1evt-zsnr7qaabgd_-tjui406.png-wh_50 "/>

▲ Set the network label and VLAN ID. This is because the Vmotion network is created and you need to tick "Use this port group for Vmotion". You do not need to tick this option when creating backup and iSCSI networks.

650) this.width=650; "Src=" Http://s3.51cto.com/wyfs02/M01/84/98/wKiom1eVt_-zvdgkAABaA8mIFiM969.png-wh_500x0-wm_3 -wmp_4-s_1376800890.png "title=" 11.png "alt=" Wkiom1evt_-zvdgkaabaa8mifim969.png-wh_50 "/>

▲ set the IP and subnet masks. The default gateway is to manage the network gateway, do not change, otherwise it will cause the management port can not be ping pass.

In this case, the VMotion (Backup, ISCSI) Vmkernel Port cannot be ping through the external machine, but can communicate between the two machines.

650) this.width=650; "Src=" Http://s5.51cto.com/wyfs02/M02/84/98/wKioL1eVuBWDGEunAABMnTXr-tM598.png-wh_500x0-wm_3 -wmp_4-s_1254208880.png "title=" 12.png "alt=" Wkiol1evubwdgeunaabmntxr-tm598.png-wh_50 "/>

▲ Summary. Click the Finish button to complete the setup

Create Backup, iSCSI networks in the same way.

650) this.width=650; "Src=" Http://s5.51cto.com/wyfs02/M01/84/98/wKioL1eVuCqDyR2eAADBNoWOU-k243.png-wh_500x0-wm_3 -wmp_4-s_1157905022.png "title=" 22.png "alt=" Wkiol1evucqdyr2eaadbnowou-k243.png-wh_50 "/>

▲ Viewing network situation changes in the main network configuration

At this point, ESXI01 's network configuration is complete. On the ESXI02 host, make the same configuration (IP is not the same).

650) this.width=650; "Src=" Http://s1.51cto.com/wyfs02/M00/84/98/wKioL1eVuDviJ-xEAACHH5W-rGI177.png-wh_500x0-wm_3 -wmp_4-s_1779420057.png "title=" 26.png "alt=" Wkiol1evudvij-xeaachh5w-rgi177.png-wh_50 "/>

▲ in esxi01 ping esxi02 each network port, can ping pass, then the network configuration has been completed successfully.

At this point, the basic configuration of the ESXi host in Vcenter is completed successfully.

In the currently built environment, you can use the host's local storage for virtual machine creation and management. This situation is only centrally managed by vcenter compared to the ESXi host alone. But the powerful features of vcenter are not being played out.

There is still much work to be done to build a complete and efficient vcenter environment. such as adding shared storage, cluster management, resource pool management, and other future articles will be introduced.

This article is from the "One Tree Qing Jin" blog, please be sure to keep this source http://sunshyfangtian.blog.51cto.com/1405751/1829656

vsphere Deployment family of 07--vcenter management ESXi hosts