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

Background introduction

At present, vSphere has released the latest version 6.5.But in many production environments, the vSphere5.1 version is still used. This article will describe the installation process of vCenter5.1 in detail.

Implementation steps

First, install. Net framework3.5

In the experimental environment, we install SQL and vCenter on the same host (strongly not recommended in the production environment). Net framework3.5 is needed to install SQL, and this feature needs to be installed in windows before installation.

Because IIS is installed when installing .net framework3.5 and port 80 is contended with vcenter server, it is recommended that the IIS management console be installed to facilitate the modification of the IIS port.

Second, install the MSSQL database

1. Insert the MSSQL CD and select a fresh installation from the installation tab

two。 Keep the default options to the feature selection interface, and select the database engine service and administrative tools

3. Keep the default options to the server configuration interface, set SQL Agent to start automatically, click to use the same account for all SQL services, and enter the set service startup account and password

4. In the database engine configuration interface, it is recommended to select mixed mode and set the sa account password, and specify the current user as the SQL administrator until the installation is completed.

5. After the installation is complete, check the SQL configuration Manager to see if the SQL and agent services start properly.

6. Type netstat-abn at the command prompt of the host to see if port 1433 for SQL service is in a normal listening state. You can see that port 80 is occupied by installing IIS when you install .net framework3.5.

7. Through the IIS Manager in the administrative tools, change the trial port of the default web site when IIS is installed or remove the site to release port 80

8. Enter netstat-abn again at the command prompt to see that port 80 has been released

Install 64-bit ODBC data source

1. Create a database called vcdb for vcenter through the SQL management interface

two。 Start-manage tools-data sources (ODBC) use SQL local client to add a system DSN

3. Enter the data source name and SQL server address, and set the ID and password of the login user

4. After changing the default database to the vcdb database dedicated to vcenter, keep the default options until the end, and test whether the connection is normal

Fourth, install the SSO database

In the vcenter server5.1 version, SSO still comes with a database, and SSO has not had a database since version 5.5. Version 5.1 in order to facilitate SSO users to create databases, create and delete scripts are prepared for different databases on the vcenter CD-ROM Single Sign On\ DBScripts\ SSOServer\ schema.

1. Three scripts are needed for creation. The two scripts in the red box are used for deletion. First, open sql management studio and execute the setuptablespace script.

two。 You can see the name of the created database and the location where it is stored. Set it as needed and click execute. After successful execution, you can see the created database and the storage files in the corresponding location.

3. Execute the script after executing the setupusers script to create the user and changing the contents in the red box to a preplanned password

4. Finally, run the createschema script, which runs directly without any modification.

5. Install SSO

1. Select the install vcenter single sign on option in the CD of vcenter, because it is in workgroup mode, there will be a warning of not joining AD.

two。 Since it is the first sso, choose to create the master node and set the type to basic sso (sso supports only one default source, that is, localos account, and the default administrator is only the local account of basic sso. When the sso is highly available, the rest of the sso nodes can only log in through domain\ user)

3. Set the password for the sso administrator and select the existing database

4. Fill in according to the database name, user, password set when creating the sso database, and set the FQDN or IP address (it is recommended to use FQDN at all times), leaving the default options until the end of the installation

5. Installing version 5.1 of sso sometimes causes errors in the data schema, which will be rolled back automatically when you click OK. After the roll is over, you can install sso again and you can go through the

6. Install Inventory Service

1. Click the install inventory service option. Since there is no DNS, enter the IP address here in FQDN.

two。 Select the list size according to the actual environment and register the information with SSO, keeping the default options until the end of the installation

7. Install vcenter server

1. Choose to install vcenter server. Since IIS is also on this host, you will be prompted with a web warning. We have deleted the IIS default site before, so we don't need to worry about it here.

two。 Select the vcdb data source you created earlier and enter the password of the sa user

3. Fill in the IP address at the fully qualified domain name and select to create an independent instance

4. Sharing a server with vcenter and SQL is not recommended because vcenter chamber pots use port 80

5. Select the list size according to the actual situation and register with SSO

6. Specify the administrator for vcenter server. It should be noted that in the version after 5.5, the domain administrator (administrator@vsphere.local) of sso is set as the administrator of vcenter, and the identified user is set as the administrator of vcenter. We mentioned earlier that the default identification source of sso is localos users and is limited to basic localos users. Users of other identification sources need to log in using domain\ user or user@domain. So here we set the administrator group on the local computer as the administrator of vcenter, or we can cancel the check box of "this administrator is a user group" and specify a user of the local system (administrator) or a user of the SSO domain (admin@System-Domain) as the administrator of vcenter. Then keep the default options until the end of the installation

8. Install vsphere client and vsphere web client

When installing vsphere web client, you need to register with sso, and the rest will remain the default option until you log in using your local account through vsphere client after installation. So far, all operations are complete.

Supplementary explanation

Some friends said that vcenter could not log in normally after changing the administrator password.

You can see from the backend service that the vcenter service cannot be started, but after the password is changed back, the service can start normally.

In fact, the reason why vcenter cannot be started is that the background database and proxy server cannot be started properly.

Friends who know MSSQL know that SQL uses the specified account to start the service (the administrator user is used during installation), and the password here will not be changed after changing the administrator password, so after changing the password manually, you can start SQL normally, and vcenter can log in normally.

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.