Archive

Archive for the ‘Homelab’ Category

Starting vRealize Orchestrator Client fails with “Unable to load resources”

December 27th, 2014 No comments

As my On-Demand NSX ICM course lab is still broken I wanted to play a bit with vRealize Automation 6.2 and the embedded vRealize Orchestrator 6.0.

Read more…

Categories: Homelab Tags:

Setting up Cisco VIRL using VMware Workstation 10

December 24th, 2014 No comments

I did receive my Cisco VIRL download link yesterday and after a couple of minutes waiting (do use a download manager as they recommend, without it would abort a couple of times for me) I finally got the OVA and key file as well.

Read more…

Categories: CCNA DC, Certification, Homelab Tags:

Migrating vCenter Server 5.5 from Server 2008 R2 to Server 2012 R2

August 28th, 2014 No comments

I got a request from one of our Technical Account Managers last week as one of his customers wanted to migrate vCenter Server 5.5 from a physical machine to a virtual machine. During that move the operating system should also change.

VMware actually does have a kb article on how to achieve this but it seems to be only validated up to version 5.0.

Migrating vCenter Server to a different host machine

Since SSO was introduced in version 5.1 the procedure should take that into account and therefore will change slightly.

DisclaimerThis is not a tested or officially approved procedure by VMware at any means, use at your own risks, don’t come to me complaining if everything breaks, DO A BACKUP!

Read more…

Categories: Homelab Tags:

Setting up a small lab CA on Windows 2012 R2 for vSphere certificate replacement

July 27th, 2014 No comments


Sure I can, so let’s go. Same assumptions as in the last post, this is not intended to be secure or anything, it should just serve the purpose of being easy to setup and work out of the box while being able to create certificates with Derek Seaman’s SSL toolkit, which should also be the requirement for the VSS Labs vCert Manager, and create vSphere basic stack compliant certificates.

Read more…

Categories: Homelab, SSL Tags:

Setting up a small lab CA on Windows 2008 R2 for vSphere certificate replacement

July 27th, 2014 No comments

Derek Seaman has done a great job describing on how to create a template for VMware View on 2008 and how to set up an intermediate CA structure in Windows Server 2012R2.

I tried going through the latter and found the procedure pretty elaborate for my own lab purposes so I thought about setting up a CA that still will work with his SSL toolkit but would be set up in about 10 minutes.

Read more…

Categories: Homelab, SSL Tags:

Changing the host name of vCenter Server 5.5 without reinstalling

June 1st, 2014 4 comments

And another twitter request that leads up to some experimenting of what you can do without relying on the installer.

Challenge accepted. The victim VC will be my own lab environment VC so this better works in the end. Additional information was provided by Jason which would make this procedure possible, the vCenter Server was a self contained instance without running any dependencies from the upper stack.

DisclaimerThis is not a tested or officially approved procedure by VMware at any means, use at your own risks, don’t come to me complaining if everything breaks, DO A BACKUP! The proper way would be a reinstall of the binary packages against existing databases.

Read more…

Categories: Homelab, SSL, SSO Tags:

vCert Manager – Installation

May 11th, 2014 No comments

As Michael Webster pointed out on twitter vExperts have the possibility to test out the vCert Manager from VSS Labs.

After a little back and forth with Michael due to some email issues I finally received the download and test license last week.

This will be a short series on how to install the product, integrate it with a Windows CA, request, extend and replace certificates for hosts and vCenter Server components and finally see if it actually can solve my “nasty” lab in which I pretty much reproduced every customer issue that I ran into so far in one single VM.

Unlike mentioned on the VSS Labs website the tool can actually cope with vCenter Server and ESXi 5.5.

Read more…

Categories: Homelab, SSL Tags:

Why Sysprep is important …

November 2nd, 2013 No comments

Trying to be time and space efficient in a reproduction for a colleague I tried to set up a multi domain forest for some SSO issues a customer is experiencing.

The promote of the first domain controller went fairly smooth but 2 others experienced some issues during the promote process.

dcpromo

Simply clicking yes just brought up the same screen a few seconds later. As I had to change the computer name of that particular VM which I wanted to promote due to another error I tried to find out if an orphaned child domain was present due to the earlier failure but neither ldifde nor ntdsutil could find any existing child domains.

dcpromo2

dcpromo3

Clicking no in the installation wizard gave the clue I needed, I had used a duplicate SID for a computer.

dcpromo4

That was when I remember that to save some space on the SSD I had used the linked clone feature of VMware Workstation. A quick check with PsGetsid from the sysinternals suite confirmed the issue.

After sysprepping the systems I could finally create the desired forest structure required by my colleague.

Categories: Homelab Tags:

Why DNS is important … #2

August 26th, 2013 No comments

While writing up objective 2.3 I tried to enable VXLAN for my clusters and ran into the following issue.

vxlanerror2

Naively clicking on “Resolve” did not doing anything good to actually resolve it so I had a look at the tasks and events of the single hosts.

vxlanerror3

So it looks like it is failing to actually install the required agent on the host. I found this weird as the vCloud Agent could be pushed just fine, so I had a look at the esxupdate.log on one of the hosts.

vxlanerror1

It looks like the shortname of the vCenter server could not be resolved, a quick check with nslookup on the host confirmed this, only the FQDN of my vCenter could be resolved. So I went ahead and added the appropriate search domain to my ESXi configuration which actually fixed the issue as the “Resolve” button was working just fine now.

vxlanerror4

Categories: Homelab Tags:

Why DNS is important…

July 19th, 2013 2 comments

I finally managed to actually configure all the shared storage options I needed (and guess the opendedup appliance will need to make way for a less RAM and CPU consuming FreeNAS or homebrew NFS appliance).

VSM setup was extremely straight forward and also the configuration of the first vCloud Director cell looked very promising after I enabled connections from the public network in the Windows firewall on Port 1433…

Still I would only see a blank screen when trying to connect to the vCloud Director landing page.

vcd_failed_start

I never had a look at vCloud Director logs so far but there aren’t that many in the logs directory, so I took an educated guess.

vcloud-container-info.log:
2013-07-16 22:04:25,679 | INFO | pool-inittracker-1-thread-1 | ServiceInitializationTracker | Application initialization detailed status report: 0% complete
com.vmware.vcloud.common-util Subsystem Status: [WAITING]
com.vmware.vcloud.api-framework Subsystem Status: [WAITING]
com.vmware.vcloud.consoleproxy Subsystem Status: [WAITING]
com.vmware.vcloud.common-vmomi Subsystem Status: [WAITING]
com.vmware.vcloud.jax-rs-activator Subsystem Status: [WAITING]
com.vmware.pbm.placementengine Subsystem Status: [WAITING]
com.vmware.vcloud.vim-proxy Subsystem Status: [WAITING]
com.vmware.vcloud.fabric.foundation Subsystem Status: [WAITING]
com.vmware.vcloud.fabric.storage Subsystem Status: [WAITING]
com.vmware.vcloud.fabric.compute Subsystem Status: [WAITING]
com.vmware.vcloud.fabric.net Subsystem Status: [WAITING]
com.vmware.vcloud.backend-core Subsystem Status: [WAITING]
com.vmware.vcloud.ui.configuration Subsystem Status: [WAITING]
com.vmware.vcloud.imagetransfer-server Subsystem Status: [WAITING]
com.vmware.vcloud.rest-api-handlers Subsystem Status: [WAITING]
com.vmware.vcloud.jax-rs-servlet Subsystem Status: [WAITING]
com.vmware.vcloud.ui-vcloud-webapp Subsystem Status: [WAITING]
|
2013-07-16 22:04:32,928 | ERROR | SpringOsgiExtenderThread-3 | StdSchedulerFactory | Couldn’t generate instance Id! |
org.quartz.SchedulerException: Couldn’t get host name! [See nested exception: java.net.UnknownHostException: vcd1.vcloud.lab: vcd1.vcloud.lab]
at org.quartz.simpl.SimpleInstanceIdGenerator.generateInstanceId(SimpleInstanceIdGenerator.java:36)
at org.quartz.impl.StdSchedulerFactory.instantiate(StdSchedulerFactory.java:1167)
at org.quartz.impl.StdSchedulerFactory.getScheduler(StdSchedulerFactory.java:1451)
at com.vmware.vcloud.scheduler.impl.QuartzSchedulerFactory.createInContext(QuartzSchedulerFactory.java:91)
at com.vmware.vcloud.scheduler.impl.QuartzSchedulerFactory.createScheduler(QuartzSchedulerFactory.java:76)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

[…]

Caused by: org.springframework.beans.factory.BeanDefinitionStoreException: Factory method [public static org.quartz.Scheduler com.vmware.vcloud.scheduler.impl.QuartzSchedulerFactory.createScheduler(com.vmware.vcloud.common.configuration.ConfigurationService) throws org.quartz.SchedulerException] threw exception; nested exception is java.lang.IllegalStateException: Cannot run without an instance id.
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:157)
at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:570)
… 29 more
Caused by: java.lang.IllegalStateException: Cannot run without an instance id.
at org.quartz.impl.StdSchedulerFactory.instantiate(StdSchedulerFactory.java:1172)
at org.quartz.impl.StdSchedulerFactory.getScheduler(StdSchedulerFactory.java:1451)
at com.vmware.vcloud.scheduler.impl.QuartzSchedulerFactory.createInContext(QuartzSchedulerFactory.java:91)
at com.vmware.vcloud.scheduler.impl.QuartzSchedulerFactory.createScheduler(QuartzSchedulerFactory.java:76)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:145)
… 30 more

Well looks like we cannot get an instance id which prevents the service from starting up correctly. The reason for failing to get an instance id seems to be that we cannot resolve the hostname vcd1.vcloud.lab. A quick check with nslookup proofs that I obviously forgot to make the entry in the DNS server.

nslookup vcd1.vcloud.lab
Server: 192.168.10.10
Address: 192.168.10.10#53

** server can’t find vcd1.vcloud.lab: NXDOMAIN

After adding the hostname to the DNS server and a quick restart of the service my lab finally seems to be good to go for good now.

vcd_starting

Categories: Homelab Tags: