Vcenter's lessons-in order to be lazy for 5 minutes it took a day to find the wrong

Beans yesterday did a very stupid thing, in order to lazy 5 minutes results took a day to solve the problems caused. Write down to warning.

This is the way things go, colleagues need me to set up a new SMTP server forward mail to Office365, the beans do not bother to build a new Windows server, so directly intended to be on the existing Windows 2012 Vcenter installed on top of it. At the same time because I think this thing is very simple, so also did not consider any backup rollback problem, directly to get started to do. Half an hour later, iis,smtp wait for the settings are good, mail forwarding also work, restart the server after the problem arises-my VMware VCenter service does not start?!! According to the log error, it seems to be unable to connect the SQL Server, restart the corresponding SQL service, SSO service, vcenter service problem remains the same.

Later thought, this problem is probably caused by IIS, estimated that a port is occupied, I if directly rollback before the operation estimated to return to normal, the result I am lazy and do a more of a thing, I see the corresponding virtual machine has a long ago to do the snapshot, in fact I do not remember when it was done, Because my name was mentally retarded, it was called before change, but then I immediately recovered the snapshot without hesitation. This snapshot is actually what I did 6 months ago (again because the lazy did not delete), because more than 60 days, and the trust between the ad has been destroyed, after the reply I even login ad can not go to the bird. So, I re-retired domain, add domain, log in, and then exasperate see Vcenter Service successfully started.

But good things always twists. I thought it was successful, but the bindings for SSO and AD have been disconnected. I log in to the Web client with a domain account, surprised to see that vcenter is empty, empty, empty ~ ~. Online research, probably need to re-bind SSO and AD, but the problem is that vcenter is not built by me, the local administrator account [email protected] I do not know the password.

Fortunately, the official KB to force, in the vcenter server inside a program can reset the password. Reference

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2034608

Based on the Help document, reset the password, log in to the Web Client, rebind SSO and AD, set the domain as the default, and then reconfigure the access rights for the domain user. After completing these steps, my domain account is finally able to successfully log in to the vsphere client and Web client. Finally, it's a relief to breathe.

After I signed in, I didn't finish my breath. Inside a large pile of red fork, found all the host's HA agent disconnects the link, in fact, vcenter simply can not control the host, direct error.

650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M02/82/FF/wKioL1doeLDQSx7aAAA7eGthNWQ073.png "title=" 1.PNG " alt= "Wkiol1doeldqsx7aaaa7egthnwq073.png"/>

The beans restart the corresponding HOSTD and VPXD services on the host, manage the network, but with the eggs, what the hell is going on? According to his error, read more than 10 KB did not find a suitable solution, staring at the log file for half a day did not find a useful hint. I finally remembered that I had seen the problem, and the goods were related to my snapshot. I wrote a blog about this.

http://beanxyz.blog.51cto.com/5570417/1723429

In short, my snapshot was done before upgrading the vcenter version, after recovering the snapshot, now my console version is higher than vcenter

Version, so you cannot connect. Load the corresponding version of the image, after upgrading vcenter, everything is back to normal.

Summary:

1. The products of different manufacturers should not be used on a server, because there is no telling what will conflict. Do not lazy mix together, in fact I have a ready-made template, the generation of a virtual machine is just 5 minutes.

2. Before you make changes, you need to consider the steps to roll back, even if you have made many changes. For example, make a simple snapshot.

3. The name of the snapshot should give a specific time, or it may be forgotten every few days.

4. Snapshots do not need to be deleted in a timely manner, or not only affect performance, but also may mislead later operations.

But at the very least, fix the mistakes you made.

This article is from the "Mapo Tofu" blog, please be sure to keep this source http://beanxyz.blog.51cto.com/5570417/1791224

Vcenter's lessons-in order to be lazy for 5 minutes it took a day to find the wrong