When I tried to upgrade my vCenter 5.0U1 Server to 5.1, all seemed to go well, up until the the moment vCenter tried to register with SSO.
I received an error message “Error 29107. The service or solution user is already registered. Check Vm_ssoreg.log in system temporary folder for details”
I checked this log, but it did not really point me in to the right direction.
Then I found a post in the 5.1 beta archive that said the unique identifier for a service to register with SSO is the Common Name from its certificate. Continue reading
In a vSphere environment I am working on we use VMware vShield Edge to do firewalling, NAT and terminate VPNs for customers.
On several occasions we where not able to make config changes to some of our VSE devices when we tried to publish the changes we made from within vShield Manager. Whenever we tried to publish the changes, we received an error message in vShield Manager it could not reach the vShield Edge device we where trying to configure.
Next to that, we noticed a lot off errors in the vShield Manager System Events tab for this specific Edge Device regarding “Multiple heartbeats missed from appliance”
An other thing we noticed was the VMware Tools for this specific VSE device did not seem to be running.
We decided to open a case at VMware and where told this is a know issue with the version of vShield we are running (5.0.1) and this will be fixed in a future version. (It is not fixed in version 5.0.2 that was released recently) Continue reading
A while ago I posted an article on LUN connectivity issues with Storage vMotion on EMC VNX when using VAAI we experienced.
Today I did received an e-mail from EMC they are able to reproduce our issues in their lab, which is an important step to get these issues resolved, since we can only do limited tests in our production environment. Great news to start the weekend. Will update again when I get more details on this.
Today I received a tweet from Chad Sakac, SVP Global SE at EMC, that he will be discussing some of the questions and concerns I raised in my blog post Challenges when upgrading environment with EMC CX4 to vSphere 5 and mixed CX4/VNX environment in next weeks Chad’s Choice WebEx, and in a blog post on his Virtual Geek blog.
Subjects for this call will be: Continue reading
Yesterday I wrote an article on issues when using a combination of CX4 and VNX in a vSphere 5 environment since ESX5 does not support on VAAI according to VMware and the VNX does. Simple solution would be to disable VAAI on all ESX5 hosts, but in that case your VNXes would also loose VAAI. Victor Forde pointed me to a blog post by Chris Wahl titeled “Forcing the NMP Plugin for Microsoft Clustering LUNs on vSphere” (good post by the way)
When reading this article, I realized you can not only use the array vendor and model strings to assign the VAAI filter driver to an array, but you might also be able to use the location (the combination of adapter, target, channel and LUN) for a device to assign the VAAI filter and VAAI Plugin to a specific array.
In short, you would need to remove the default VAAI filter and VAAI plugin rules for vendor=DGC and model=* and replace them by claim rules for based on the location where you would use the target identifier to filter on, for the array that would need to have VAAI enabled.
Unfortunately I don’t have a VNX in my lab (Someone at EMC that wants to trade my VNXe and a case of beer for a VNX? 😉 ) so I am not able to test if this would really do the trick. Continue reading
Yesterday my good friend Gabrie van Zanten from Gabes Virtual World asked the following question on twitter:
My first reaction was “Why would Gabe want to disable VAAI on a per array basis isn the first place?” so I asked.
His answer was pretty simple and straight forward. He was working on an environment where ESX5 hosts had both EMC CX4s and VNXes connected, and VAAI was not supported on vSphere 5 for CX4, so he had to disable VAAI for the CX4’s and wanted to leave it on for the VNXes. Continue reading
vCenter Operations Manager for View is a new VMware product that correlates al kinds of performance figures in a VMware View environment. More info on vCenter Operations Manager for View can be found here
vCenter Operations Manager for View basicaly is a set of front end tools for vCenter Operations Manager 5 that gets info from all View components.
Whenever you connect to the vCenter Operations Manager 5 UI VM, you automatically end up at the default login page for vCenter Operations Manager 5, which made me enter my credentials at the wrong place all the time, since this instance is only used for vCenter Operations Manager for View.
The correct way to access vCenter Operations Manager for View is go to the
https://<UI VM>/vcops-custom url, which off course can be bookmarked, but since I access this system from multiple desktops, I was looking for an easier way to do this, and succeeded.
It’s pretty simple, Continue reading
In the release notes for the View client for iPad version 1.5 I read one of the new features for the client is:
Save password option if administrator enables new VMware View 5.1 policy
Since I already upgraded my Lab/Demo environment to View 5.1, and this would be a very welcome feature for demo purposes (I would not use this in a production environment due to the security issues this might cause) I decided to enable it.
Because the release notes talked about a policy, I kind of expected this option to be either in an ADM template, or in the policy section of the Connection Server.
It was not …. Continue reading
Today I was working on upgrading some hosts in a vSphere 5 environment that is using Cisco Nexus 1000V virtual switches. I imported the extension bundle in Update Manager, created a baseline, and scanned the hosts. After a couple of seconds , I got a message in vCenter telling me the scan failed:
Scan entity <hostname> Host cannot download files from VMware vSphere Update Manager patch store. Check the network connectivity and firewall setup, and check esxupdate logs for details. Continue reading
The last few weeks I have been working on some serious issues in an environment where we used vSphere 5 with an EMC VNX storage array. All seemed to run fine, but whenever we started a Storage vMotion, we noticed all kinds of strange errors we where not expecting at all.
We saw messages regarding write-quiesced VMFS volumes, we lost paths. and in some cases, the Storage vMotions did not complete at all.
During these Storage vMotions we noticed datastore latency peaked at more then 5 seconds on the source and destination LUN’s.