使用vSphere Client登录vCenter Server 6.0时可能会出现如下报错信息：
Login to the query service failed.
The server could not interpret the communication from the client. (The remote server returned an error: (500) Internal Server Error.)
这是因为在登录vSphere Client时勾选了”Use Windows session credentials“。试试取消它。
相关知识库链接：Searching the Inventory with the vSphere Client fails (2143566)
You may see following problem if you login vCenter Server 6.0 by vSphere Client:
Login to the query service failed.
The server could not interpret the communication from the client. (The remote server returned an error: (500) Internal Server Error.)
That’s because “Use Windows session credentials” checkbox is selected. Deselect it and give it a try.
Refer KB Searching the Inventory with the vSphere Client fails (2143566)
Just a quick post. When virtual machine cannot get DHCP IP address the first thing you want to check is firewall. Whatever Windows firewall or physical firewall. You should make sure UDP port 67 and 68 are not blocked. Otherwise you will see the virtual machine gets 169.x.x.x IP address only.
The two ports is required for DHCP client to query IP addresses. The methodology is introduced in RFC document.
DHCP uses UDP as its transport protocol. DHCP messages from a client
to a server are sent to the ‘DHCP server’ port (67), and DHCP
messages from a server to a client are sent to the ‘DHCP client’ port
(68). A server with multiple network address (e.g., a multi-homed
host) MAY use any of its network addresses in outgoing DHCP messages.
I also got some ideas in this post.
You may see ‘Adobe Flash Player Out of Date’ on Chrome when you open vSphere Web Client. Click the text Chrome will update Flash Player automatically. But in some cases it doesn’t work due to maybe your Chrome is controlled by company policy or internet problem to Adobe.com. I found an article to show how to offline fix the issue. You can download Flash Player for Opera and Chromium-based browsers – PPAPI in official Adobe KB article.
You may also want to check out my other articles about Flash issue on browsers.
Flash menu appears when right click on vSphere Web Client in Chrome
Cannot open vSphere Web Client on IE11 on Windows 8.1
Slight network latency may cause application problem on sensitive virtual machines. Even the network responding time is just 3 or 7 ms. There is a way to improve the stability of responding latency – Enable RSS on NIC.
Network traffic is handled by single CPU core when RSS is disabled. Enable it will distribute the workload to 4 cores by default. You can increase CPU for RSS by change registry.
To summarize the solution. Go to Device Manager -> NIC properties -> Advance -> Find RSS option and enable it. You will see 2 – 3 network drops when applying it.
You can refer following articles for detail.
Poor network performance or high network latency on Windows virtual machines
Virtual Receive-side Scaling in Windows Server 2012 R2
Regarding increase CPU for RSS. Read following article to learn how to modify it.
Setting the Number of RSS Processors
If your company implemented firewall and blocked public NTP server, you may see installation of vRealize Operation Manager pending on ./install.sh on console. That’s because the installer tries to negotiate with NTP server http://www.iana.org. The firewall blocked the traffic.
VMware TAM Manager Shan told me there are two options on firewall to block traffic: REJECT and DROP. REJECT means firewall responding to the request and let source device knows it’s rejected. DROP means firewall immediately ignores the request and no responding to source device. Looks like there is a bug in vROPs code that it hung if NTP request gets drop and no responding.
The workaround is create a port group without physical uplinks and install vRealize Operation Manager. Then move it to proper network after installation is completed. You can configure correct IP addresses when import the OVF file so later on you just need simply move the network.
The smartd service can leads to ESXi 6.0 or 6.5 hosts no responding due to out of memory. I see that issue on ESXi 6.0 U2 and U3 both. I would recommend stay on ESXi 5.5 U3 at this moment.
We do see the issue persist even after stop smartd service.
Check out VMware official KB.
Just noticed a gap here. If your ESXi host is 5.5 Update 2 or earlier version, you are not able to choose ‘Windows Server 2016’ as operating system when you create virtual machine. It’s addressed in KB https://kb.vmware.com/kb/2132789.
There is a KB describes how to fix right click issue in IE on vSphere Web Client. But my problem was in Chrome. I searched a lot in internet but no lucky till today.
The problem was flash menu appears when I right click anything in vSphere Web Client in Chrome. I have two computers that both has Chrome installed but one has issue, other one works fine. I compared version of Chrome, noticed working one was 55.x, problematic one was 49.x. The issue gone after upgraded to 57.x.
After dig into that problem, looks like Google fixed the problem on version 54.0.2840 that there was a bug related to right click. Check out release notes here.
I own Raspberry Pi 1 and 2 both. I used to do some small projects and learn Python on its. It’s great computer to learn scripting and Linux. But not something can be used in daily based.
I was excited when I hear Raspberry Pi foundation released Pi 3. Thanks foundation brought our world a powerful, cheap and flexible computer that can replace my laptop. In general, I think Pi 3 can be used for daily work in GUI interface. It comes with embedded WiFi, Bluetooth and quad-core 1.2GHz CPU! It frees up the 4 USB ports so I can use it for other purpose.
I have a laptop that motherboard was dead, screen still works. So I bought driver board for the LED screen. Connected Pi 3 to the driver board by HDMI cable. The official Pi 2 case is compatible with Pi 3 except power LED in the other side. I use the latest OS “RASPBIAN JESSIE WITH PIXEL“. I have to say the graphical interface is awesome! It’s more like a modern, real computer. I use default browser Chromium which is similar with Chrome PC version. I also installed “Google Input Tool” extension on Chromium so I can input Chinese. Since most of my work on websites so I don’t have to install input tool on OS. And I saw some interface problem when use Chinese input tool for Linux. I also tried bluetooth headset, not working well. So I turned to USB headset, it works perfectly.
I opened 10 more tabs in Chromium just like how do I use my PC. I also ran a online website to streaming music to USB headset. Wrote blog, brows photos, edit files…etc. I didn’t see any performance issue so far. I guess my high performance TF card may helped. I bought Samsung 64GB UHS-1 Class10 for my Pi 3.
VDP在未来的vSphere版本中将不再继续更新。在2022年以前对于现有的VDP客户没有影响。如果客户想迁移到其他备份方案，VMware提供限定时间内的免费迁移至Dell EMC Avamar Virtual Edition的促销。客户依旧可以通过vCenter的存储API把第三方备份解决方案和vCenter整合。
Just a quick update that VDP will discontinued in future release of vSphere. It doesn`t impact to existing customers till 2022. VMware offers free migration to Dell EMC Avamar Virtual Edition in limited time if customers want to move to other backup solution. Customers can also use other 3rd party backup solutions to integrate with vCenter Server via storage API.
Read this FAQ for detail. VMware products lifecycle matrix for your reference.
Just noticed a issue that nothing reported in ‘Hardware Status‘ tab of ESXi hosts in vSphere Web Client. KB 2112847 gives a solution but not works for me. The feature can be used to monitor hardware failures. I figured out a way to workaround it. You just need to login by Administrator account and click ‘Update‘ button under ‘Monitor‘ – ‘Hardware Status‘ for each ESXi host. You will get the status after few minutes.
You may see following error when you scanning ESXi hosts by vCenter Update Manager.
Host cannot download files from VMware vSphere Update Manager patch store. Check the network connectivity and
firewall setup, and check esxupdate logs for details.
You also see similar logs in /var/log/esxupdate.log.
[Errno -2] Name or service not known
The root cause could be following:
- ESXi host cannot resolve DNS name of vCenter Update Manager Server.
- One of the DNS servers incorrect if you set multiple DNS servers on ESXi host.
Virtual appliance is future of how VMware delivery their product to customers. It’s pain to migrate from vCenter Server Windows version to virtual appliance. The only way was build up new virtual appliance and move everything out of Windows vCenter Server. The challenge is you lost data if you have integrated vCenter Server with other VMware products, or using DVS.
VMware released vCenter Server Migration Tool after VMworld 2016. It gave me confidence to give it a try. I assume vCenter Server is embedded SSO. I did the migration 2 or 3 times, following is summary of my experience. The migration tool only support migrate vCenter Server 5.5 windows edition to vCenter Server 6.0 U2.
- vCenter Server is more like core services today since lot of 3rd party software call vCenter API to interactive with VMs. You may have some products integrated with vCenter Server already. Please upgrade to vCenter 6 compatible version before migration.
- I suggest create a local account on source vCenter Server if your server is domain member. You can login back source vCenter by local account in case migration failed.
- vCenter Server Migration Tool applies temporary IP address on destination vCenter virtual appliance during migration. It’s used to communicate with source vCenter. Please register a temporary IP address for destination vCenter Server.
- A helper VM is required to run migration image. Please make sure you have a free Windows VM be ready to mount migration image.
- SQL database is exported to source vCenter Server if you want migrate performance and event data. So you need to make sure enough space on C: drive on source vCenter. The free space should be much bigger than vCenter database size.
- Of course you need a vCenter Server 6 license key since old key doesn’t support the version.
- Some cases show migration process stopped during export SQL database. That’s because memory of source vCenter is too small. Please make sure RAM of source vCenter should be equal or greater than destination vCenter Server.
- The other tricky is database table. You may see migration processes is completed but destination vCenter Server doesn’t come up, and no data actually imported. That’s because ‘checksum‘ column existing in table [dbo].[VMO_ResourceElementContent] in vCenter DB. You can run following SQL query to remove it before migration.
alter table dbo.VMO_ResourceElementContent drop column checksum;
The items above can be done anytime before the migration window. Following steps should be token during migration.
- You need to disable firewall and anti-virus software on old vCenter to avoid communication issue between Migration Assistant and new vCenter Server.
- To avoid any unstable, resource contention, or potential network connectivity lost issue, I suggest temporarily disable DRS and HA on source and destination cluster if they are virtual machine.
- Copy Migration Assistant from migration image to old vCenter.
- Take snapshot on old vCenter and backup database of old vCenter.
- Connect to console of source vCenter and run Migration Assistant.
- Mount vCenter Server 6 U2m image on helper VM. Launch vCenter migration. The migration process is straightforward. I wouldn’t introduce more here.
Basically you need to revert all the temporary changes made before. Such as delete snapshot and DB backup, enable DRS and HA, and disable vNIC on source vCenter Server to avoid any human error.
I wrote an article to introducing how to integrate PowerCLI with PowerShell and PowerShell ISE. VMware just released PowerCLI 6.5 R1, it includes lot of new features and modules. And somehow my way doesn’t work. Following is new way to integrate PowerCLI 6.5 with PowerShell and PowerShell ISE in Windows 10.
PowerShell and PowerShell ISE both have it own $profile. So we need to do two times.
Before we start
Please make sure your PowerShell execution policy is not restricted. You can get the setting by run following command:
- Open PowerShell window. Run following command to confirm profile file is not existing.
If return is ‘False’, go to step 2.
If return is ‘True’, Backup the file and go to step 3.
- Run following command if the profile file doesn’t existing.
New-Item -Path $profile -type file -force | Out-Null
The return above should be ‘True’. Profile file is created.
- Run following command to include VMware PowerCLI modules in PowerShell.
Add-Content -Path $profile -value "# Load Windows PowerShell cmdlets for managing vSphere `r`n. 'C:\Program Files (x86)\VMware\Infrastructure\PowerCLI\Scripts\Initialize-PowerCLIEnvironment.ps1'"
The blue text above maybe different in your environment base upon where your PowerCLI is installed.
PowerShell ISE Integration
PowerShell ISE process is same to PowerShell, only different is all the operation should be completed in PowerShell ISE window.
Reboot is not required in my environment. But anyhow please reboot if you see any issue.
The processes above integrate PowerCLI 6.5 with PowerCLI and PowerCLI ISE for current user only. If you want to integrate for all users on the machine, you need to refer to this article.
New B200 M4 blades can running on Intel v4 processors. You may see discovery issue if your UCSM firmware version lower than 2.2.7c. I hit that problem few days ago when I install a new M4 blade. The FSM hung on 58% a real long time and failed eventually.
Found this link on Microsoft website. Just want to make a notes on my blog. Thanks community!
If you have VMware Workstation and VMware Remote Console both installed on Windows 10 you may see vCenter virtual machine console in vSphere Web Client is opened by VMware Workstation instead of VMware Remote Console. If you see same case your VMware Remote Console may be hijacked. I call it “hijack” since there is no easy way to revert it back.
如果你的Windows 10电脑上装了VMware Workstation和VMware Remote Console，当你在vSphere Web Client里打开运行在vCenter上的虚拟机控制台时，VMware Workstation可能会代替VMware Remote Console自动连接到控制台。恭喜！你的VMware Remote Console被劫持了。这个问题解决起来比较复杂所以我叫它“劫持”。
用vSphere Web Client打开虚拟机的控制台时可以会遇到报错 “Unable to connect to MKS: Could not locate vmware-authd executable“。
You may get error “Unable to connect to MKS: Could not locate vmware-authd executable” when open virtual machine console in vSphere Web Client.
Today my co-worker asked me a question about memory spec on ESXi hosts. There are two types of memory, LRDIMM and RDIMM available on hardware vendor’s list. Which one is best choice?
Size value is too long when I grab snapshot size of a VM. It’s something like the screenshots below.
I got a request few weeks ago. Reporting virtual machines that powered off more than 3 days. I didn’t find out-of-box report in vROps can do that. I had to create customized one. Following is how I did.
If you are multi-language IT Pro you may want to show articles in multiple languages just like me. I use Polylang in my blog to switch English and Chinese version. I used to add “Language Switcher” tag in my articles. It’s manual process that I had to remember the tag in somewhere, copy and past it to articles when I was writing. It’s frustration to repeat it in every article. Another problem was I have to add “Read More” tag in each article before I add “Language Switcher” tag. That’s because each post shows a switcher in home page if I don’t do that. It confuses Polylang which URL each article should goes. I want to find a perfect way to fix this problem! Here we go…
也许你和我这种挨踢砖家一样奇葩，用多种语言写博客。我的WordPress使用Polylang显示文章的中英文版本。一般我需要在文章里加一个”Language Switcher”标签来显示语言切换。添加这个标签不是那么容易，我得把它记在某个地方，需要的时候复制、粘贴到文章里。在每篇文章里添加这个标记有点儿麻烦。另外，这个标记必须配合”Read More”标记之后使用，如果语言切换标记出现在”Read More”之前会导致首页上出现多个语言切换标记，每个语言切换标记无法知道每篇文章对应的URL是多少。看看我是如何完美解决这个问题的吧…
有很多种方法可以用来做虚拟机快照报表。比如PowerCLI、VRTools、甚至vSphere Client本身也可以。今天我会分享如何使用vRealize Operations Manager (vROps) 6.x做自定义天数以前创建的虚拟机快照的报表。用vROps做表表的好处是可以通过计划任务自动以邮件形式发送报表，并提供PDF和CSV两种格式的表。 我在网上找到了一篇文章谈到如何用vROps实现类似报表。但要求修改vROps的规则，这可能会影响到vROps的全局计算模型。如果你的团队们需要为各自的报表设置不同的条件怎么办？
There are several ways to reporting snapshots. You can use PowerCLI, VRTools, or even vSphere Client itself. Today I will show you how to reporting by vRealize Operations Manager (vROps) 6.x. The benefit of vROps reports is you can schedule it by sending email with PDF & CSV reports. I found a post discuss how to reports by vROps. But it requests modify policy, it may impacts global calculation. What if your teams request different criteria for reports?
HPE SPP2016.04 is released. I usually test April version since it’s always stable than October or other earlier version.
HPE SPP2016.04 刚刚发布。我一般都测试4月份的版本，因为相对于10月份或者更早的版本要稳定一些。
I want to try make a remote control car by Raspberry Pi. The first question is how to power a portable Raspberry Pi? There are lot of solutions in internet. I want to find a simple, cheap and long battery life solution. Some articles introduced power bank but it overs $100 and only provides 5v output. I need some thing can provide not only 5v power for Raspberry Pi, but also more than 7v for L298N.
Cisco UCS blade system is the best blade system I used so far. Whatever the hardware, software or support is perfect. I recommend leverage the system for primary system of virtualization. UCS blade system architecture is different with HP. I feel it more likes a network system. Fabric Interconnect (FI) modules exchange data between uplinks and internal components. IOMs on each chassis controls data routing. Architecture is complicate, but it’s powerful to manage large datacenter. Talking about large datacenter, you may have hundred chassis or blades. Data goes through FIs, IOMs and blades, you could see issues on any layer. It’s hard to find out where exactly the problem is. UCS Manager provides statistics for ports just like how Cisco does on network switches. You can show statistics of a particular port. But it doesn’t tell you when and which layer it happened. I tested Cisco UCS adapter for vRealize Operation Manager before I reviewed NetApp adapter for vRealize Operation Manager. It’s developed by same company Blue Medora. I’d like to introduce few of this product, it’s just my personal review.
思科UCS刀片系列是我至今用过最好的刀片系统。无论是硬件、软件还是技术支持都堪称完美。个人推荐在大型虚拟化机房里把思科UCS作为主要设备。思科UCS刀片系统的架构和惠普的完全不同，感觉更像是个网络设备。Fabric Interconnect (FI)模块负责上联口和内部各组件之间的数据交换、IOM负责各刀箱数据路由。架构看起来很复杂，但是在管理大型数据中心时非常强大。说到大型数据中心，比如有 上百个刀箱和刀片服务器，数据要经过FI、IOM、刀片等，问题可能发生在任何层面，大型虚拟化数据中心很难找到问题的根源。UCS Manager有提供类似思科网络交换机一样的计数器功能，可以显示每一个端口的计数情况，但是这个监控工具不会告诉你什么时间、在哪个层面发生了问题 。在测试NetApp存储性能监控组件之前我有幸测试了vRealize Operations Manager 6的Cisco UCS性能监控组件。该组建同样由Blue Medora开发。以下简单介绍一下，只是我的个人观点 。
NetApp released Virtual Storage Console (VSC) 6.1 for vCenter 6.0. The solution is only support vSphere Web Client now. I did some testing on my lab, faced a very special case.
NetApp发布了Virtual Storage Console (VSC) 6.1 对应 vCenter 6.0。这个产品现在只支持vSphere Web Client了。我在实验环境下做了一些测试，遇到一个非常特殊的案例。
Today I got a strange problem about share folder. Some virtual machines cannot access network share path. It gave me Unspecified Error 0x80004005 when I opened a share folder on explorer. It gave me The network path was not found 0x80070035 when I opened same share folder by clicking Start – Run.
今天遇到了一个很奇怪的问题。有些虚拟机无法访问网络共享文件夹。当用文件浏览器打开共享文件夹时会弹出Unspecified Error 0x80004005错误。如果在开始 – 运行 里打开相同的文件夹又会提示The network path was not found 0x80070035。
vRealize Operation Manager 6 （又叫vROps）是vCenter Operation Manager的全新版本，我从vCenter Operation Manager还是1.0时就开始使用了，很喜欢自我学习和动态阀值这两个功能。但是这款产品只能监控虚拟层面，如果可以监控存储层面就完美了。在比较大的vSphere环境中虚拟机是共享ESXi数据存储（datastore）的，如果少数虚拟机产生很高的IO，可能会影响到其他处于同一个存储上的虚拟机。想象一下，如果你有100个LUN跑在一个NetApp存储上，300个虚拟机在使用这100个LUN，某日用户说他们的虚拟机很慢，但是他们并没有跑什么应用，这时候就会比较难判断到底是哪儿出了问题，因为虚拟机可能共享同一个数据存储（datastore），数据存储存建于LUN上，LUN 可能来自某个聚合（Aggregate），并且多个LUN可能来自同一个物理磁盘。vCenter Operation Manager 在5.x时代有提供一款NetApp存储监控组件，但问题是很难把vSphere的数据存储（Datastore）和NetApp存储的设备关联起来。
vRealize Operation Manager 6 (aka vROps) is new generation of vCenter Operation Manager. I started to use vCenter Operation Manager since version 1.0. I like the idea of self-learning and dynamic threshold. But the product only monitors virtualization layer. It would be perfect if it’s able to monitor under layer storage. In large vSphere environment, virtual machines share IO capacity of datastores. If few virtual machines running high disk IO it may lead to other virtual machines get performance degrading in same storage. Think about you have 100 datastores come from a NetApp filer, and 300 virtual machines running on its. One user says their virtual machine is slow but no workload from applications end. It hard to say where the latency comes from because multiple virtual machines may share same datastore, multiple LUNs share same aggregate, and maybe same physical disks. vCenter Operation Manager provided NetApp Adapter for 5.x few years ago. But the problem was it’s too hard to associate storage objects with vSphere datastore objects.