This article describes the scenario where you will experience a timeout from vCenter while deploying the Trend Micro Deep Security Appliance 9.0 (DSVA) on an ESXi 5.5 Host. I got some information from Trend Micro about this issue, which can simply be resolved by retrying the deployment.
So what happens? The first time you try to Deploy the DSVA (and complete the wizard):
https://virtualkenneth.com/2014/08/18/deploying-dsva-esxi-5-5-fails-first-attempt/
During some recent Trend Micro Deep Security 9.0 implementations I’ve come across an issue while “Preparing” the ESXi 5.5 Host for Deep Security. This process is initiated from the Deep Security Manager and should normally install the Trend Micro Filter Driver and add some settings to the ESXi 5.5 Host.
While preparing the ESXi 5.5 Host
You will eventually get the error message: “The installation transaction failed”.
This problem is described in this VMware KB article and a work around is described, however, this work around is not complete.
As VMware describes you need to manually install the Filter Driver and you need to add a Virtual Machine group named “vmservice-trend-pg” to the configuration. This VM Portgroup needs to be added to the same vswitch which has been created by vShield.
https://virtualkenneth.com/2014/08/15/prepare-esxi-5-5-host-within-deep-security-9-0/
While installing new HP BL460c Gen8’s (Xeon E5-2680 v2) we discovered some strange behavior while setting the HP Power Profile setting to “Maximum Performance”. It appears that this setting causes the ESXi 5.1 Installer to not see the Internal SD-Card as storage device anymore.
Default BIOS Settings give us this, which is good:
https://virtualkenneth.com/2014/08/07/bl460-detecting-sd-card-esxi-5-1-installation/
Recently I have been experiencing some troubles with VMware Host Profiles, Auto Deploy and the stateful install of ESXi 5.1 (Update 1). After the Host Profile gets applied, the system eventually times out with the message: “The request failed because the remote server took too long to respond” as indicated on the screenshot below.
https://virtualkenneth.com/2013/10/24/auto-deploy-esxi-stateful-install-multiple-luns-connected-fails/
This blog post highlights the technical difference on how vCenter SRM4 and SRM5 do failover with Hitachi’s Virtual Storage Platform (HDS VSP). Credits to Saravanan Mahalingam for delivering this information.
SRM 4
SRM 5
So while SRM4 is reversing the replication automatically, SRM5 needs the “manual” Re-protect option for that. This is important to know in case you need to guarantee replication before VM’s get booted on the Recovery Site (as part of the run book).
For more information on how to implement HDS VSP with vCenter Site Recovery Manager 5 see these resources:
https://virtualkenneth.com/2013/06/18/differences-between-srm4-and-srm5-using-hds-storage/
While designing for vSphere Auto Deploy you may want to group (categorize) your ESXi Hosts and attach a deploy rule (rule set) to them:
You specify the behavior of the Auto Deploy server by using a set of rules written in Power CLI. The Auto Deploy rule engine checks the rule set for
matching host patterns to decide which items (image profile, host profile, or vCenter Server location) to provision each host with.
So for instance, by creating a deploy rule (rule set) which matches on hardware type you could add all the same hardware to a specific cluster (with a specific host profile). But what if you got different vSphere Clusters, identical hardware and don’t want to make an exception by manually adding a pattern like hostname or mac address every time? In that case you could consider using the hardware Asset Tag to categorize your ESXi Hosts.
https://virtualkenneth.com/2013/06/17/vsphere-auto-deploy-consider-asset-tag-to-categorize-esxi-hosts/
During configuration and testing of the vSphere Authentication Proxy we discovered some problems that make the use of the Authentication Proxy very unreliable within multi Domain Controller environments. In our case we are using the Authentication Proxy in conjunction with vSphere Auto Deploy but the problem also occurs in scenario’s without Auto Deploy.
https://virtualkenneth.com/2013/04/24/vsphere-authentication-proxy-cannot-complete-login-due-to-an-incorrect-user-name-or-password/
Within this article I will share some of the challenges faced while implementing a VMware Auto Deploy environment with DHCP for the Management Network.
The environment uses an Infoblox DHCP/DNS appliance but contains some good-to-know things that are not Infoblox specific, so keep on reading.
DHCP is configured to use mac-address reservations to ensure that each ESXi Host receives a static IP address. After starting ESXi from PXE Boot you will get the well-known ESXi Boot Screen:
https://virtualkenneth.com/2012/12/14/esxi-dns-hostname-lookup-with-dhcp/
Within this article I will try to give you a clear vision on the HP Virtual Connect FlexFabric Mappings that HP uses to facilitate their blades with NIC’s and HBA’s. If you are looking for the Flex-10 mappings click here.
In our example we use the HP BL460 Gen8 blade with a FlexibleLOM (LAN on Motherboard) Adapter and no additional mezzanine cards. HP’s quote about the FlexibleLOM:
In past server generations, the adapter is embedded on the system motherboard as a LOM (LAN on motherboard). If a customer desired a different kind of networking adapter, they would need to purchase a standup adapter and install it in a slot in the server.
Now with many ProLiant Gen8 servers, our customers can now choose the type of network adapter they want. This new Flexible LOM provides our customer the ability to customize their server’s networking of today and the ability to change to meet future needs without overhauling server infrastructure.
https://virtualkenneth.com/2012/11/26/understanding-hp-virtual-connect-flexfabric-mappings-with-vmware-vsphere/
While troubleshooting the vSphere Authentication Proxy (vSphere 5.1) I ran into a bug which will I highlight in this article.
After successfully installing the Authentication Proxy I discovered an error message in the C:\ProgramData\VMware\vSphere Authentication Proxy\logs\camadapter.log:
2012-xx-xx 14:03:35: Failed to bind CAM website with CTL
2012-xx-xx 14:03:35: Failed to initialize CAMAdapter.
https://virtualkenneth.com/2012/11/19/vsphere-authentication-proxy-failed-to-bind-cam-website-with-ctl/
