Posts

Showing posts from July, 2020

Exception when uploading OVA to vCenter when using Proxy

Image
With the recent version vCenter 7.0.0b there seems still being an issue when having HTTP / HTTPS proxy configured and trying to import an OVA / OVF. This is the error message you will see most likely: Failed to deploy OVF package. ThrowableProxy.cause A general system error occurred: Transfer failed: Server not trusted: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target, note that HTTP/s proxy is configured for the transfer. A quick workaround is to disable Proxy via VAMI and only enable it when you need id to download updates via Lifecycle Manager or for vCenter updates. I have a support case open for this, let´s see if there will be a fix soon. cheers!

Using HPE Nimble witness in a docker container

When we started to deploy our second HPE Nimble "Automatic Switchover" pair I decided to change deployment mode for the witness to a docker based deployment because there can only run a single instance per VM and I don´t want to have unnecessary lazy VMs sitting around. Be aware there is not official support for this!  I tested this type of deployment twice and it worked fine for me. Find the needed files in my Github repository  https://github.com/weidi/nimble-witness-docker Versions Witness binary is updated every once and then so please make sure you are using the right dockerfile and download the right binary for your array version. Build download needed binary via InfoSight.hpe.com place it in the same directory as the Dockerfile change password in Dockerfile run  docker build -t nimble/witnessd . Run make sure you have docker-compose setup use  docker-compose up -d  to start the container if needed adjust the exposed port in the composefile so you can run multiple insta

Hidden Floppy device attached to a VM therefore still shown on an empty datastore

I recently discovered a situation where a virtual machine was still showing on a datastore that was literally empty. There where no files leftover and also nothing like ISO or configuration stuff pointed to the old datastore. The problem was, the VM had a floppy device configured that was not visible through the vSphere UI It showed up when using PowerCLI get-vm VM_Name| Get-FloppyDrive FloppyImagePath      HostDevice                   RemoteDevice ---------------      ----------                   ------------ [Datastore... Removing it was done also via PowerCLI. get-vm VM_Name|| Get-FloppyDrive | Remove-FloppyDrive And magically VM is no longer registerd to that Datastore and i can go on decommissioning it. cheers!

Remove vSAN Fileservices configuration

Image
When you try removing the vSAN File Services config completely there is no easy option by today including vCenter 7.0.0b Especially when you want to change the Network configuration (portgroup and IP addresses) you can´t do this from the UI. After disabling and re enabling File Services on the UI the wizard will show you the old settings but wont let you reconfigure it. Basically it´s because the settings are already deployed with the vAPP that´s still there. You need to remove the OVF Files that are sitting inside the vCenter Appliance. Login to vCenter via ssh using root delete all files below "/storage/updatemgr/vsan/fileService/" Reenable vSAN Fileservices in the UI and you can now start from scratch Now it´s up to VMware to change this and getting a UI option for it. cheers!

Howto: Offline deploy vSAN Fileservices OR: Howto manually download required vSAN FS ovf

Image
Today I had the issue that automatic downloading the OVF for vSAN Fileservices failed for whatever reason. Thus I had to take the manual approach but downloading only the .ovf file via the given Link is not enough. Required are overall 6 files that are needed for the Appliance to work. You will find hints to the filename when opening the ovf file and just replace the last part of the downloadlink with the appropriate file.