I ran into an error the other day, when updating an IBM based vSphere 6.0 environment using Update Manager, and I want to share my solution with you and myself, so I do not need to find it the next time I run into it.
ERROR: The host returns esxupdate error code:15. The package manager transactions is not successful. Check the update Manager log files and esxupdate.log files for more details.
Continue reading VMware ESXi Update on IBM Servers fail
Are you looking to Upgrade Mirage and move it to a new server, or are you just looking to move Horizon Mirage to a new server, this article will describe what you need to do.
Continue reading Upgrade VMware Horizon Mirage to new server
Network health check is a very useful feature that was introduced with vSphere 5.1 vDS.
What does it do?
The purpose is to test if the VLANs, MTU and Load Balancing settings you defined are actually working. The old way of doing this would be to disconnect all port except one, by either doing a shutdown on the switch port, or pulling out the cable, and then testing, with a VM, if every VLAN still works. This can be a very lengthy process if you have many adapters, but also a necessary step if you want a stable environment.
If you want to know more about how it check the different settings, Joseph Griffiths did a good article on this you can read here: http://blog.jgriffiths.org/?p=877
So why would you ever disable this feature?
Well the health check feature generates a lot of mac table entries as explained in VMware KB 2034795.
An example given is that you have 35 Hosts with 2 Network Adapters each, and 60 VLANs. This will generate (35 * 2 * 60) 4200 mac table entries in your physical switches. And as you can see, this quickly increases. Some switches only has room for 32.000 records or less. Continue reading Should you enable Network health check for your Distributed Virtual Switches
If you need to search your vSphere Datastores for orphaned VMDK files, Luc Dekens made a script that can help you.
Another possibility is to use rvTools.
Tired of having to update all your servers manually, or with Microsoft WSUS, but without control?
Are you tired of wasting 1-2 hours, every time you deploy a template, for it to install all the latest patches?
Why not automate it the easy way?
Continue reading Automating Windows Update
Today we will look at how to enable REST on phpIPAM. This is an essential part when integrating with vRealize Orchestrator, since REST is an excellent interface for automation.
REST might scare you at first, but don’t loose faith, you will soon enough begin to like it, when you vRealize the power it brings.
Continue reading Free IPAM solution – 3. Enabling REST
Trying to remember the password for all of your different web interfaces?
Remember one less password, by enabling Active Directory authentication for phpIPAM.
Continue reading Free IPAM solution – 2. Enabling LDAP Authentication
Quick guide to getting a self signed certificate configured for Apache on Ubuntu 16.04.
All credits go to Justin Ellingwood. There is a link to his article at the bottom of this page. This is just a quick summery of what needs to be done to get SSL working, based on his article.
I do not recommend using self-signed certificates in production, as it does not provide any security what so ever! Deploy a signed certificate from your internal 2-Tier PKI infrastructure. If you do not have an internal PKI infrastructure, your need to get one!
Continue reading Enable SSL on Apache2 (Self-Signed)
Are you tired of using Excel for managing you IP addresses?
Why not use an IPAM DB to keep track of your VLANs, subnets and IP addresses?
An IPAM solution is a vital building block in an automated environment. Lets go through how you can setup a Free IPAM DB for use with vRealize Orchestrator and vRealize Automation.
Continue reading Free IPAM solution – 1. Installing phpIPAM
I just upgraded the vCenter in my test lab, and I got an error after the first part of the process. When it was about to migrate data from the old VCSA 6.0 Server.
I restarted to process but this time is was unable to get information from my source VCSA server. In the log I had the following errors:
2016-11-16T16:42:03.649Z - info: VM Identifier for Source VC: vm-108
2016-11-16T16:42:03.784Z - debug: initiateFileTransferFromGuest error: ServerFaultCode: A general system error occurred: vix error codes = (1, 4294967294).
2016-11-16T16:42:03.785Z - debug: Failed to get fileTransferInfo:ServerFaultCode: A general system error occurred: vix error codes = (1, 4294967294).
2016-11-16T16:42:03.785Z - debug: Failed to get url of file in guest vm:ServerFaultCode: A general system error occurred: vix error codes = (1, 4294967294).
2016-11-16T16:42:03.785Z - error: Error in getting fileData for nodeType. Error: ServerFaultCode: A general system error occurred: vix error codes = (1, 4294967294).
2016-11-16T16:42:03.785Z - error: Failed to read the nodetype, Error: A general system error occurred: vix error codes = (1, 4294967294).
2016-11-16T16:42:03.786Z - error: sourcePrecheck: error in getting source Info: ServerFaultCode: A general system error occurred: vix error codes = (1, 4294967294).
I quickly discovered the reason. My root password was expired and it wanted me to create a new password for root.
Continue reading vCenter 6.5 Upgrade fails with error: vix error codes = (1, 4294967294)