Shulou(Shulou.com)06/02 Report--

Blogger QQ:819594300

Blog address: http://zpf666.blog.51cto.com/

Friends who have any questions can contact the blogger, the blogger will help you answer, thank you for your support!

1. The experimental topology is as follows

2. Experimental environment:

As the scale of BENET company continues to expand, it needs to build more servers to achieve private cloud, so it needs to recruit multiple virtualization engineers, and each virtualization engineer manages different types of servers, assuming that the company has three servers, namely, web server, mail server and database server. The virtualization engineers are: Zhang San, Li Si and Wang Wu. Now Zhang San can only manage the web server, Li Si can only manage the mail server, and Wang Wu can only manage the database server. In addition, the company's supervisor cluo can manage all servers, deputy supervisor meixi can also manage all servers, but can only view servers, can make snapshots, can modify hardware configuration, but can not shut down, can not clone, can not make templates.

Third, the experimental steps:

1. Install a linux virtual machine first

2. Use cloning technology to clone a linux virtual machine.

3. Convert the original linux virtual machine into a template

4. Build a new linux virtual machine using templates

5. Power on the new linux virtual machine, and then configure the ip address to ping iscsi.

6. Install vmtools on the new linux virtual machine

And take a snapshot of the new linux virtual mechanism (select memory snapshot and silent snapshot)

7. Set up 5 users and set permissions according to the requirements of the experimental environment.

8. Use 5 users to test permissions separately

9. Use ha to build a highly available cluster

Note: there is time to study how to convert a real server into a virtual machine and store it in esxi.

Vmtools

1. The mouse does not need ctrl+alt to switch.

2. The mouse moves fast.

3. Drag and drop data directly

4. Click the red square to turn off the phone.

5. You can create a silent snapshot

6. Share virtual machine resources (spit out excess cpu and memory resources)

.

The process of the experiment:

1. Install a virtual machine, a brand new virtual machine. (note: when creating a virtual machine, do not click independent when creating a virtual machine (because when you click independent to do a snapshot later, you cannot do a snapshot because the virtual machine created independently is not affected by snapshots). In addition, the installed virtual machine must play √ in all the options for development).

Preparations for this lab:

1) Openfiler needs to add 4 50G disks and make two RAID0 volumes. For the later HA high availability, two storage must be used (at least two storage must be used. The system defaults to backup)

2) each of the two ESXi requires at least 5 network adapters (that is, network cards). This is also because the high availability can be used, and the default standard network cards Switc0 and iscsi need to be backed up, otherwise there will be the following error warning when making high availability:

3) the firewall of SQL/vServer should be turned off (you can make an exception if you know the port number). This is because if the firewall is not turned off when it is highly available, the following error will be reported:

2. Use cloning technology to clone a linux virtual machine.

Right-click the virtual machine to be cloned

3. Convert the original linux virtual machine into a template

5. Power on the new linux virtual machine, and then configure the ip address to ping the iscsi.

4. Build a new linux virtual machine using templates

5. Power on the new linux virtual machine, and then configure the ip address to ping the iscsi.

6. Install vmtools on the new linux virtual machine

And take a snapshot of the new linux virtual mechanism (select memory snapshot and silent snapshot)

First, before installing vmtools, check to see if the virtual machine is still connected to the CD (local, ESXi host or data storage ISO, if directly disconnected graphically)

Then complete the following operations

According to the requirements of the experimental environment, set up 5 users and set permissions (to demonstrate, I can only be one user here)

(in addition, expand some knowledge: how to add your own permissions)

Apply the authority of Zhang San to Zhang San:

9. Use ha to do high availability clustering. First of all, make sure that the data of the virtual machine used in the experiment must be on the memory, not on ESXi, otherwise you will not be able to do high availability, and don't forget to add a network card to the default standard switch vSwitch0 and iscsi switch for backup. (only one can be used when creating an iscsi network card. Otherwise, when you add iscsi to the storage adapter, you can't see the iscsi network card, wait for the iscsi to be added in the storage adapter, and then fill in a network card for backup. There are still vSenter firewalls to be turned off)

Then complete the following steps:

Here is the name of a cluster:

Drag and drop two ESXi hosts to the cluster with the mouse:

When there is a small exclamation point in the ESXi host, it means that the network card has not been backed up, the memory has been backed up, and the firewall of vcenter has not been turned off. If all the preparatory work is done, the small exclamation point still exists, then the exclamation point can be made to disappear by the following methods:

At this point, you can see that 100.1 is the host of the cluster:

At this point, you can see that 100.2 is a subordinate to the cluster, subordinate to:

You can see that the host ESXi of the linux for muban virtual machine is 192.168.100.1:

You can see that the host ESXi of the linux-clone virtual machine is 192.168.100.2:

Open linux for muban this virtual machine assigns a permanent ip address of 192.168.100.201

To open the client's cmd side, "ping192.168.100.201-t"

Ping this virtual machine all the time, and it will have a good effect:

Disconnect all network cards of the 192.168.100.1 ESXi host (equivalent to the downtime of this ESXi host)

You will see that the request timed out due to the 192.168.100.1 downtime:

After a while, you can see that 192.168.100.2 becomes the host of the HA cluster due to the outage of 192.168.100.1.

You can see the effect of the highly available cluster, and the host ownership of the virtual machine Linux for muban becomes 192.168.100.2:

If you look at the effect of the client's ping, you can see that the red box is caused by the 192.168.100.1 downtime and then the cluster has a short interruption, and finally the virtual machine returns to normal:

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.