VMware vsphere FAQ Rollup (16)

Tag: blank target single error color

the Troubleshooting Installation SSO error: Error 20010.failed to configure Lookupservice problem

Fault status
The following error is prompted when installing Vcenter Single sign on this component:

Error 20010.failed to configure Lookupservice

650) this.width=650; "Style=" border-right-0px; border-top-width:0px; border-bottom-width:0px; border-left-width:0px "title=" clip_image001 "border=" 0 "alt=" clip_image001 "src=" file:///C:/Users/Administrator/ Appdata/local/temp/windowslivewriter1286139640/supfiles5956e20a/clip_image001_thumb[1].jpg "width=" 419 "height=" 191 "/>

Fault analysis
This problem is generally caused by AD, DNS, time and so on;
Solution Solutions
1, check whether the computer name in the ad is normal;
2, check the DNS server resolution inside the forward and reverse address resolution, and recommend clearing the DNS cache and expired records, and then restart the DNS server;
3, pay attention to the Vcenter server time must be synchronized with the Ad server;
4. Note that the computer name of the vcenter server must not contain special characters;
5. Note that the password configuration of vcenter single sing does not include unusual special characters such as @.
6. Make sure the firewall of the vcenter server is turned off.

161 unable to log on to the Windows 2000 system after P2V

Fault Status
1. After successfully completing P2V Windows 2000 physical server, you cannot log on to its virtual machine;
2, enter the user name password, the system prompts the local personal user settings loading, the Welcome window has been unable to eject;
Fault Analysis
This problem is usually due to the drive letter of the boot partition and the inconsistent system letter during initial installation;
Solution Solutions
1. Create a new virtual machine that can be started successfully, and then mount the extracted vmdk on the Windows 2000 Server;
2, after starting the new virtual machine, when this additional VMDK disk is recognized, confirm its drive letter;
3. After you change the drive letter of the boot partition, close the new virtual machine and remove the previously added VMDK;
4. Try to start the system again on the extracted Windows 2000 virtual machine.

3. IBM x3850x5 the host is disconnected from the network for no reason, and all virtual machines are disconnected

Failure phenomena

On November 13, around 8 o'clock, the VMs were found to be disconnected, the host was found to be disconnected from the vcenter, and the ESXi physical host was restarted to return to normal. At that time, the client's ESXi physical machine was the IBM x3850 X5,esxi version of 4.1 U1.

Fault analysis

Analyze results with 800 logs:

1. Query through the Compatibility list:

Http://www.vmware.com/resources/compatibility/detail.php? devicecategory=io&productid=3242&devicecategory=io&keyword=5709&page=1&display_interval=10 &sortcolumn=partner&sortorder=asc

The previous version was 2.0.7D-3VMW.

2.this issue have been observed in Bnx2 driver version 2.0.7c.

This issue are resolved in the following asynchronous Broadcom driver releases:

? esx/esxi 4.0–broadcom driver version 2.0.15g.8.v40.1? esx/esxi 4.1–broadcom driver version 2.0.15g.8.v41.1 to resolve This issue, ensure-your ESX/ESXI host has one of the these driver version installed. To download the latest Broadcom NetXtreme II Ethernet network controller driver version, see the VMware Download Center.

kb.vmware.com/kb/1029070

Solution Solutions

1. Upgrade the NIC driver to Broadcom driver version 2.0.15g.8.v40.1. Download link http://downloads.vmware.com/d/details/dt_esxi40_broadcom_bcm57xx/zhcqynqlzwhidgqlca==

2. Installation drive

Method 1

(1) Insert the drive ISO CD into the ESXi optical drive. Note: ESXi hosts use CDROM methods to compare special

~ # Vmkload_mod iso9660

Module iso9660 Loaded successfully

~ #/sbin/vsish-e Set/vmkmodules/iso9660/mount mpx.vmhba32:c0:t0:l0

~ # Ls/vmfs/volumes/cdrom #此时该到该目录即可看到光盘内容

The CD goes to the directory where the drive is located.

(2) The host enters maintenance mode and uses the command to upgrade

Esxupdate--bundle=xxxxx (driver name). zip Update

Method 2

1. Decompress the NIC driver

2. Drive zip file (bnx2-2.1.5d.v40.1-offline_bundle-446542.zip) under "Offline-bundle"

3. Upload Bnx2-2.1.5d.v40.1-offline_bundle-446542.zip to/vmfs/volumes/<datastorename>/

4. Use the following command "Esxupdate--bundle=bnx2-2.1.5d.v40.1-offline_bundle-446542.zip Update" To upgrade the driver

Method 3

1. Download the vmware-vsphere-cli and install it on your own computer;

2. Download the corresponding driver for the NIC and unzip it.

3. The host that will install the drive is set to maintenance mode by connecting Vcenterserver via Vsphereclient, right-clicking on the host and selecting "Enter Maintenance Mode" (Note that it is best to turn off the virtual machine on the host).

4. Open a command prompt (run-"cmd"), switch to VMWAREVSPHERECLI's installation directory, go to Bin, run:

>VIHOSTUPDATE.PL--SERVERXXX.XXX.XXX.XXX (this host IP)--install-bundle% Drive directory

%vmware-esx-drivers-net-igb_ 400.3.2.10-1vmw.2.17.249663.493750offline-bundleoffline-bundleint-intel-lad-ddk-igb-3.2.10-offline_ Bundle-493750.zip (This parameter is the directory where your driver is located)

You will then be prompted to enter a user name and password, which will then execute the command for driver installation, which can be seen in the word vsphereclient. The installation of the NIC driver is completed after the command is completed. You can see the NIC.

How to query the driver of the network card, you can use the following command:

A. Log in to the ESXi server using the root user;

B. # ethtool-i Vmnic0

164 . Update Manager problems with the inability to use ODBC

Failure phenomena:

Adding ODBC in the system cannot be used in Update Manager

Solution:
Because Update Manager ODBC is 32-bit, and the Vcenter System Management tools ODBC is 64-bit, there is an incompatibility problem, you need to enter: C:\windows\syswow64\odbcad32.exe in the Run bar. You can then add ODBC.

165 . Vcops5.6 monitoring of the health state to vcenter is 0

Fault Status:

After vcenter Operations 5.6 deployment, the health state of the actual vcenter server is 0, as shown in:

Fault Analysis:

Looking for a half day, found that vsphere replication Management Server was not running, causing this

Solution:

Open the "com.vmware.vchms" configuration plugin in mob, and after removing this for VR plugin, fix it:

After removal, the health status is as shown, OK:

Then take a look at the vsphere Web client vcenter Solutions Manager, which is normal.

- 6. Vsphere Replication unable to pair VRMS server hint VRM server generic error

Fault status

Try to configure SRM with vsphere replication, however, when attempting to configure the Vrms connection, you are prompted with the following error:
VRM server Generic Error.please Troubleshooting information.the Detailed exception is: "Unexpected status code:404".

Fault analysis
This error is generally caused by fqnd problems;
Solution Solutions
Edit the Hosts file for the primary site and recovery site, as the customer chooses VCSA, so execute the following command:

1. vi/etc/hosts

2.10.10.10.10 vc01.vmanager.cn VC01

3.10.10.10.20 vc02.vmanager.cn VC02

After the modification is complete, reboot the VCSA server and do it.

167. Solve the problem of HP ESXi host continuously disconnecting from vcenter

Fault status

Hp OEM versions of ESXi 5.x systems are always automatically disconnected from vcenter, and then disconnected after a while;

Solution Solutions
1, SSH or dcui connected to the ESXi host;
2. Remove the HP OEM version license module by executing the following command:
#esxcli software vib remove-n hp-esx-license--no-live-install
3. Restart the ESXi host

650) this.width=650; "Style=" border-right-0px; border-top-width:0px; border-bottom-width:0px; border-left-width:0px "title=" clip_image003 "border=" 0 "alt=" clip_image003 "src=" file:///C:/Users/Administrator/ Appdata/local/temp/windowslivewriter1286139640/supfiles5956e20a/clip_image003_thumb[1].jpg "width=" 448 "height=" 233 "/>

- 8. Resolve exit Lockdown mode will disable root access issues

A recent user prompt as shown in the failure:

650) this.width=650; "Style=" border-right-0px; border-top-width:0px; border-bottom-width:0px; border-left-width:0px "title=" clip_image005 "border=" 0 "alt=" clip_image005 "src=" file:///C:/Users/Administrator/ Appdata/local/temp/windowslivewriter1286139640/supfiles5956e20a/clip_image005_thumb[1].jpg "width=" 464 "height=" "/>
Regarding the use of lockdown mode, I think it should be clear to everyone that it is used to secure ESXi host as shown in:
650) this.width=650; "Style=" border-right-0px; border-top-width:0px; border-bottom-width:0px; border-left-width:0px "title=" clip_image007 "border=" 0 "alt=" clip_image007 "src=" file:///C:/Users/Administrator/ Appdata/local/temp/windowslivewriter1286139640/supfiles5956e20a/clip_image007_thumb[1].jpg "width=" 470 "height=" 173 "/>
After testing, the problem is that when the ESXi host enters Mockdown mode and immediately removes root, it causes the dcui.access role to be more privileged at this point than lockdown mode, which can cause this problem, The reason is that lockdown mode works, and the role it invokes is in the particular role of dcui.access;
Recalling the whole process of lockdown mode is that when the ESXi host joins the Vcenter, is locked by a specific permission, and then through the agent to perform the lock command communication, when this permission is lost, the lock mode is invalid, but at this time the root permission is not, Therefore, the above problems will arise;
Because lockdown mode relies on the role of the vcenter server to define the dcui.access permissions of the call, when Vcenter is down, to restore root access to the ESXi host, the only time for ESXi The host has access to the root account, as shown in:
650) this.width=650; "Style=" border-right-0px; border-top-width:0px; border-bottom-width:0px; border-left-width:0px "title=" clip_image009 "border=" 0 "alt=" clip_image009 "src=" file:///C:/Users/Administrator/ Appdata/local/temp/windowslivewriter1286139640/supfiles5956e20a/clip_image009_thumb[1].jpg "width=" 485 "height=" "/>
Go back to ESXi host and see the current Permision list's User/group, as shown in:
650) this.width=650; "Style=" border-right-0px; border-top-width:0px; border-bottom-width:0px; border-left-width:0px "title=" clip_image011 "border=" 0 "alt=" clip_image011 "src=" file:///C:/Users/Administrator/ Appdata/local/temp/windowslivewriter1286139640/supfiles5956e20a/clip_image011_thumb[1].jpg "width=" 475 "height=" "/>
The user list shown here contains the root user and the ADMIN02 user as well as the Vpxuser and dcui users, all of which have administrator permissions;
After you enter ESXi host into lockdown mode and then dcui.access the list to change root to Admin02, as shown in:
650) this.width=650; "Style=" border-right-0px; border-top-width:0px; border-bottom-width:0px; border-left-width:0px "title=" clip_image013 "border=" 0 "alt=" clip_image013 "src=" file:///C:/Users/Administrator/ Appdata/local/temp/windowslivewriter1286139640/supfiles5956e20a/clip_image013_thumb[1].jpg "width=" 479 "height=" 109 "/>
Then, when ESXi host is entered into maintenance mode, attempting to log on to ESXi host again will fail, as shown in:
650) this.width=650; "Style=" border-right-0px; border-top-width:0px; border-bottom-width:0px; border-left-width:0px "title=" clip_image015 "border=" 0 "alt=" clip_image015 "src=" file:///C:/Users/Administrator/ Appdata/local/temp/windowslivewriter1286139640/supfiles5956e20a/clip_image015_thumb[1].jpg "width=" "height=" 235 "/>
Go to the Dcui interface, enter the username admin02 and password as shown, and then you can log in as it is in the Dcui.access list, but when you log in to ESXi again, as shown, the root user wood has:
650) this.width=650; "Style=" border-right-0px; border-top-width:0px; border-bottom-width:0px; border-left-width:0px "title=" clip_image017 "border=" 0 "alt=" clip_image017 "src=" file:///C:/Users/Administrator/ Appdata/local/temp/windowslivewriter1286139640/supfiles5956e20a/clip_image017_thumb[1].jpg "width=" 373 "height=" 172 "/>
The root account is the only user name that has permissions, so if root is no longer available, even if the other username have administrator privileges, you still cannot exit lockdown mode of ESXi.

- 9. Installing the HP CIM driver for ESXi 5.x hosts

CIM Full Name Common information model, which is used to communicate between ESXi host and hardware sensor;
It exists to facilitate communication between the ESXI host and the hardware so that the state of the hardware can be queried, as shown in:

650) this.width=650; "Style=" border-right-0px; border-top-width:0px; border-bottom-width:0px; border-left-width:0px "title=" clip_image019 "border=" 0 "alt=" clip_image019 "src=" file:///C:/Users/Administrator/ Appdata/local/temp/windowslivewriter1286139640/supfiles5956e20a/clip_image019_thumb[1].jpg "width=" 511 "height=" "/>
When the HP CIM driver is deployed, clicking on health status displays the status information as shown:
650) this.width=650;" Style= "border-right-0px; border-top-width:0px; border-bottom-width:0px; border-left-width:0px "title=" clip_image021 "border=" 0 "alt=" clip_image021 "src=" file:///C:/Users/Administrator/ Appdata/local/temp/windowslivewriter1286139640/supfiles5956e20a/clip_image021_thumb[1].jpg "width=" 505 "height=" 294 "/>
with this CIM driver, for the ESXI host hardware health monitoring can be implemented as desired, but sometimes may encounter the built-in CIM driver and hardware version mismatch problem, then, at this time, May need to go to the service organ network download the latest for ESXi host driver to install, natural is designated official website, here is introduced when HP, so as shown in:

650) this.width=650; "Style=" border-right-0px; border-top-width:0px; border-bottom-width:0px; border-left-width:0px "title=" clip_image023 "border=" 0 "alt=" clip_image023 "src=" file:///C:/Users/Administrator/ Appdata/local/temp/windowslivewriter1286139640/supfiles5956e20a/clip_image023_thumb[1].jpg "width=" 521 "height=" "/>

After the download, it is installed, the installation steps are as follows:

1. Enter the DCUI command navigation interface to the ESXi host and execute the command as shown:

#esxcli Software Vib install-d/vmfs/xxxx/xxx.zip

Or execute the VCLI remote command line:

#esxcli-S x.x.x.x-u root-p password software vib install-d/vmfs/xxxx/xxx.zip
When the execution is complete, as shown:

650) this.width=650; "Style=" border-right-0px; border-top-width:0px; border-bottom-width:0px; border-left-width:0px "title=" clip_image025 "border=" 0 "alt=" clip_image025 "src=" file:///C:/Users/Administrator/ Appdata/local/temp/windowslivewriter1286139640/supfiles5956e20a/clip_image025_thumb[1].jpg "width=" 545 "height=" "/>

The corresponding relationship of VM virtual machine snapshot

About Snapshots:

Virtual Machine cannot is powered on.

Error Message:cannot Open Disk. VMDK file or one of the snapshot disks it depends on.

Virtual Disk header file is missing.

Guest operating system fails when creating snapshots.

Windows guest operating system fails with a blue screens when a snapshot is created.

Guest Operating systems exhibits strange behavior when a snapshot is created.

The virtual machine to power on using the snapshot:

1. Log in to the ESX Host service console.

2. Type grep ' ^cid ' <filename.vmdk> to see the content of the virtual disk header file. Do not use the <filename-flat.vmdk> as, which is the actual content of the virtual disk.
The output appears similar to:
Cid=fb183c20
Take note of the CID.

3. Open the snapshot header file with a text editor. If there is more than one snapshot in the tree, it's the first snapshot in the tree (usually the one with filename-000001 . vmdk).

4. Locate the line that contains the string parentcid=.

5. Replace everything to the right of the equal sign with the CID obtained from step 2.

6. Save and exit the file.

7. Power on the virtual machine.

8. Http://kb.vmware.com/kb/1004232

Note: When a guest OS has multiple hard disks, when a snapshot is made to the guest OS, the snapshots for each drive will each have one (for example, the guest has 3 hard disks, and the first snapshot will generate 3 more vmdk), named as follows:
Before the guest OS makes a snapshot:

650) this.width=650; "Style=" border-right-0px; border-top-width:0px; border-bottom-width:0px; border-left-width:0px "title=" clip_image027 "border=" 0 "alt=" clip_image027 "src=" file:///C:/Users/Administrator/ Appdata/local/temp/windowslivewriter1286139640/supfiles5956e20a/clip_image027_thumb[1].jpg "width=" 569 "height=" 334 "/>

After the first snapshot:

650) this.width=650; "Style=" border-right-0px; border-top-width:0px; border-bottom-width:0px; border-left-width:0px "title=" clip_image029 "border=" 0 "alt=" clip_image029 "src=" file:///C:/Users/Administrator/ Appdata/local/temp/windowslivewriter1286139640/supfiles5956e20a/clip_image029_thumb[2].jpg "width=" 515 "height=" 637 "/>

After the second snapshot:

650) this.width=650; "Style=" border-right-0px; border-top-width:0px; border-bottom-width:0px; border-left-width:0px "title=" clip_image031 "border=" 0 "alt=" clip_image031 "src=" file:///C:/Users/Administrator/ Appdata/local/temp/windowslivewriter1286139640/supfiles5956e20a/clip_image031_thumb[2].jpg "width=" 504 "height=" 683 "/>

Note: The above operation in the guest shutdown operation in the execution of the snapshot operation, when the guest boot "*000002.VMDK" the system disk in the three hard disk, the CID will change, but the parentcid will always be unchanged.

The value of the CID corresponds to "parentfilenamehint", pointing to the need for the same disk, such as "" "Parentfilenamehint=" ERIC_TEST_WIN2K31_2-000002.VMDK ""

Delete snapshot1 Status:

650) this.width=650; "Style=" border-right-0px; border-top-width:0px; border-bottom-width:0px; border-left-width:0px "title=" clip_image033 "border=" 0 "alt=" clip_image033 "src=" file:///C:/Users/Administrator/ Appdata/local/temp/windowslivewriter1286139640/supfiles5956e20a/clip_image033_thumb[3].jpg "width=" 734 "height=" 488 "/>

Finally, refer to the official kb:http://kb.vmware.com/kb/1003861

VMware vsphere FAQ Rollup (16)