Mastering VMware vSphere 6. Marshall Nick
Чтение книги онлайн.
Читать онлайн книгу Mastering VMware vSphere 6 - Marshall Nick страница 20
Название: Mastering VMware vSphere 6
Автор: Marshall Nick
Издательство: John Wiley & Sons Limited
Жанр: Зарубежная образовательная литература
isbn: 9781118925164
isbn:
2. If Autorun doesn’t automatically launch the VMware vCenter Installer (shown previously in Figure 2.11), navigate to the CD/DVD and double-click Autorun.exe.
3. On the VMware vCenter Installer main screen, click vSphere Desktop Client, and then click Install.
4. Select the language for the installer (if prompted) and click OK.
5. Click the Next button on the welcome page of the vSphere Desktop Client Installer.
6. Click the I Accept The Terms In The License Agreement check box, and then click the Next button.
7. Configure the destination folder, and then click the Next button.
8. Click the Install button to begin the installation.
9. If prompted, select I Have Read And Accept The Terms Of The License Agreement, and then click Install to install the Microsoft .NET Framework, which is a prerequisite for the vSphere Client.
10. When the .NET Framework installation completes (if applicable), click Exit to continue with the rest of the vSphere Client installation.
11. Once complete, click the Finish button to exit the installation. Restart the computer if prompted.
64-bit vs. 32-bit
Although the vSphere Client can be installed and is supported on 64-bit Windows operating systems, the vSphere Client itself remains a 32-bit application and runs in 32-bit compatibility mode.
Reconfiguring the Management Network
During the installation of ESXi, the installer creates a virtual switch – also known as a vSwitch– bound to a physical NIC. The tricky part, depending on your server hardware, is that the installer might select a different physical NIC than the one you need for correct network connectivity. Consider the scenario shown in Figure 2.12. If, for whatever reason, the ESXi installer doesn’t link the correct physical NIC to the vSwitch it creates, then you won’t have network connectivity to that host. We’ll talk more about why ESXi’s network connectivity must be configured with the correct NIC in Chapter 5, but for now just understand that this is a requirement for connectivity. Since you need network connectivity to manage the host from the vSphere Client, how do you fix this?
Figure 2.12 Network connectivity won’t be established if the ESXi installer links the wrong NIC to the management network.
The simplest fix for this problem is to unplug the network cable from the current Ethernet port in the back of the server and continue trying the remaining ports until the host is accessible, but that’s not always possible or desirable. The better way is to use the DCUI to reconfigure the management network so that it is converted the way you need it to be configured.
Perform the following steps to fix the management NIC in ESXi using the DCUI:
1. Access the console of the ESXi host, either physically or via a remote console solution such as an IP-based KVM.
2. On the ESXi home screen, shown in Figure 2.13, press F2 for Customize System/View Logs. If a root password has been set, enter that root password.
3. From the System Customization menu, select Configure Management Network and press Enter.
4. From the Configure Management Network menu, select Network Adapters and press Enter.
5. Use the spacebar to toggle which network adapter or adapters will be used for the system’s management network, as shown in Figure 2.14. Press Enter when finished.
6. Press Esc to exit the Configure Management Network menu. When prompted to apply changes and restart the management network, press Y.
After the correct NIC has been assigned to the ESXi management network, the System Customization menu provides a Test Management Network option to verify network connectivity.
7. Press Esc to log out of the System Customization menu and return to the ESXi home screen.
Figure 2.13 The ESXi home screen provides options for customizing the system and restarting or shutting down the server.
Figure 2.14 In the event the incorrect NIC is assigned to ESXi’s management network, you can select a different NIC.
The other options within the DCUI for troubleshooting management network issues are covered in detail in Chapter 5.
At this point, you should have management network connectivity to the ESXi host, and from now on you can use the vSphere Client to perform other configuration tasks, such as configuring time synchronization and name resolution.
Configuring Time Synchronization
Time synchronization in ESXi is an important configuration because the ramifications of incorrect time run deep. Although ensuring that ESXi has the correct time seems trivial, time-synchronization issues can affect features such as performance charting, SSH key expirations, NFS access, backup jobs, authentication, and more.
After the installation of ESXi or during an unattended installation of ESXi using an installation script, the host should be configured to perform time synchronization with a reliable time source. This source could be another server on your network or a time source located on the Internet. For the sake of managing time synchronization, it is easiest (and most secure) to synchronize all your servers against one reliable internal time server and then synchronize the internal time server with a reliable external Internet time server. ESXi provides a Network Time Protocol (NTP) implementation to provide this functionality.
Automating basic Configuration
Although configuring Time Synchronization or Name Resolution is quite simple, if your environment has a large number of hosts, configuration can become tedious. These kinds of changes can be scripted. You can find a number of examples on VMware community member blogs.
The simplest way to configure time synchronization for ESXi involves the vSphere Client. Perform the following steps to enable NTP using the vSphere Desktop Client:
1. Use the vSphere Desktop Client to connect directly to the ESXi host (or use the vSphere Web Client, if you have vCenter Server running at this point).
2. Select the hostname from the inventory tree on the left, and then click the Configuration tab in the details pane on the right.
3. Select Time Configuration from the Software menu.
4. Click the Properties link.
5. In the Time Configuration dialog box, select NTP Client Enabled.
6. Still in the Time Configuration dialog box, click the Options button.
7. СКАЧАТЬ