Posts tagged ‘vcenter’

Creating your own Root CA with OpenSSL on Windows, and signing vCenter or SRM certs

In This Post, I created certificates for my SRM & vCenter servers where I used a separate signing authority. What if you don’t have one, but still want to use your own certs? You create your own Root Certificate Authority (root CA) via OpenSSL. Here’s how…
Read the rest of this entry »

Creating Certificates for VMware SRM or vCenter using openSSL made easy, with Video!

Written April 4th, 2012 by
Categories: Virtualization
10 comments

Some of the documentation around creating certificates for vCenter or SRM seems to be lacking, so I documented a few steps for each and outlined the differences, also created a video :)

This can be done from any machine, as long as openssl is installed. If you’re creating/requesting multiple certs, create folders for each request and work from within there so you don’t mix them up. I use d:\cert\vcenter and d:\cert\srm. I added “D:\OpenSSL-Win32\bin\” to may path variable so it’ll work in any folder I’m in.

Read the rest of this entry »

Error 25085 – Setup failed to register VMware Update Manager extension to VMware vCenter Server

Written November 4th, 2011 by
Categories: Virtualization
1 Comment »

I upgraded my vCenter to 4.1u1 while my VUM was still 4.0 (u2 iirc).  I decided to upgrade my VUM to match, and all was going well until I got this message:

Error 25085 – Setup failed to register VMware Update Manager extension to VMware vCenter Server

Read the rest of this entry »

Script I needed to get info for multiple VMs = Get-VMInfo.ps1

Written May 5th, 2011 by
Categories: Scripts, Virtualization
2 comments

I’ve recently had a ton of requests for information about specific VMs. They want to know how many disks they have, CPU count, how much RAM, and which environment the VM resides in.

Instead of constantly searching vCenter, I wrote this quickly during the meeting to query multiple servers.
Read the rest of this entry »

System Error: vmodl.fault.hostcommunication

I upgraded one of my lab hosts to ESXi 4.1 yesterday and was plagued with this error:

System Error: vmodl.fault.hostcommunication

vmodl.fault.hostcommunication

A lot of people are getting this error without a lot of direction. As it turns out, this is because I upgraded one of my hosts to 4.1 without upgrading vCenter to 4.1. Silly me! Who would have thought that vSphere vCenter couldn’t manage a vSphere host because it’s rev is 0.1 higher?

VMware vSphere 4.1 Configuration Maximums

Written July 31st, 2010 by
Categories: Virtualization
No Comments »

ESXi 4.0 Update 1 brought with it one major update (as I pointed out here). Now that 4.1 was released on July 13th, I wanted to take a look and see if anything else major has been changed.

Biggest change was they lifted the 160 VMs per host in an 8-node HA cluster.  Now it’s the maximum of 320 VMs per host, and a maximum of 32 nodes per HA cluster.  Problem is, they imposed a maximum of 3000 VMs per cluster (standard, HA, or DRS, they no longer differentiate them), so you’d just have to find your sweet spot to maximize how you want your cluster set up.  Not that 3000 VMs per cluster is a problem, but if you ran 320 VMs on 75% of a 32-node cluster (leaving 25% for failover), that’s 7680.  That’s a difference of 4680 VMs.  At any rate, I’m glad they lifted the 40 VMs per host in a 9+ configuration.

The Configuration Maximums for 4.1 can be found here.

Here are some of the key features that have changed:

Read the rest of this entry »

Finding WWNs for HBAs in multiple ESX or ESXi hosts, standalone or clustered

**Update May 07, 2012 – Use the new script here: Updated: Finding WWNs for HBAs in ESXi hosts, now with Get-VMHostHba

When building a new cluster, your storage team (or you) may need to add several hosts into the shared storage zone. It’s a pain to go to each host, configuration, storage adapters, then copy out the WWN.

With this script, you can supply a vCenter server and Cluster/Folder/Datacenter (any logical container) and it will list all the WWNs for Fibre Channel devices. But what if you don’t have vCenter stood up yet? No problem, you can also supply a list of ESX/ESXi hosts to scan.

Shawn & I built this because we have 20 hosts we need the WWNs from to provide to our storage team, and vCenter isn’t alive yet.

Our script: Read the rest of this entry »

Designed by ThepHuck
Wordpress Themes
Scroll to Top