Tag - VMware

I’ve just hit the six month mark in my new role at VMware: Senior Cloud Solutions Architect - Service Providers. This role sees me working closely with a paired Business Development Manager, aligned to our VMware Cloud Provider Partners to design and build cloud platforms that highlight and expand on their unique offerings. It’s my first foray into the pre-sales world, and I’m loving it. I’ve really enjoyed talking to our partners, learning more about their businesses, and helping them map VMware solutions to their business objectives.

Recently I had a customer testing their vCenter Server 7.0U3e file-based restore process using the VCSA Restore Wizard. During Stage 2 (data copy) the wizard hung at 80% and did not progress for hours. No UI errors or hints as to what was happening. I had a look at the restore wizard logs and found the following: 2022-07-12T01:16:19.828Z - debug: [7]pollRpmInstallProgress:getGuestFileErr:ServerFaultCode: The object 'vim.VirtualMachine:103' has already been deleted or has not been completely created 2022-07-12T01:16:30.

While exploring vRealize Automation and SaltStack Config, I had the bright idea to expand the integrations across the vRealize Suite by automatically installing the vROPs Telegraf agent during a vRA Deployment. This would provide immediate guest OS monitoring and (optional) application monitoring to every machine deployed from vRA. What you’ll need: vRealize Automation 8.8 vRealize SaltStack Config 8.8 Integrated with vRealize Automation through either vRealize Suite Lifecycle Manager or as a standalone SaltStack instance.

If you’re ever in a position where you need to change the DNS settings on your VMware Identity Manager (vIDM) appliance, you may have noticed that vRealize Suite Lifecycle Manager (vRSLCM) doesn’t provide you with this mechanism. Luckily, the vIDM appliance itself contains “OVF Properties” within the vSphere UI. You can shutdown the appliance and modify these settings to allow the appliance network configuration to re-apply your new configurations to the guest.

I have a customer about to embark on a (relatively) large Cisco ACI upgrade, followed by a dvSwitch LACP update to Enhanced LACP. This includes updating ACI EPG policies to use the newly created LAG as the primary uplink port. Normally in the vSphere UI, you can view this per port group. But in an environment wth 12 vCenter Servers and 22 distributed switches (and a couple thousand port groups), that manual process can get out of hand pretty quick.

I was trying to install the vRealize Operations Telegraf agent on my VMs by following the documentation. I wrote the steps out in a Salt state file: unzip: pkg.installed install-telegraf: cmd.script: - source: https://cloudproxy.domain.tld/downloads/salt/download.sh - name: /tmp/download.sh -o install -v vrops.domain.tld -u admin -p p@ssw0rd - mode: '0777' Salt takes the source and puts it in the location under name, executing it with the included arguments. However, everytime it ran I would get this:

During some recent lab work, I deployed a fresh vRealize SaltStack Config 8.8 appliance in my lab and had it integrated with vRA and vIDM. On first login I found that my vIDM/vRA administrator (config admin) was unable to see the minions in SaltStack Config UI. After some trial and error and working with some others internally, I found the issue was related to the default permissions provided by the vRA IAM integration.

Cloud-Init and Hostnames First problem was Ubuntu 20.04 to properly boot from the Packer HTTP directory. I found approximately 3,125,319 blogs online all with different Ubuntu boot commands. I settled on this: boot_command = [ "c", "linux /casper/vmlinuz --- autoinstall ds=\"nocloud-net;seedfrom=http://{{.HTTPIP}}:{{.HTTPPort}}/\"", "<enter><wait>", "initrd /casper/initrd", "<enter><wait>", "boot<enter>" ] Next up was a working user-data file for the boot customisation process. I settled on a mish-mash of different examples found online: #cloud-config autoinstall: version: 1 early-commands: # Stop ssh for packer - sudo systemctl stop ssh locale: en_US keyboard: layout: en variant: us # general packages needed for machines - referenced from https://tekanaid.

In February 2022, I reached an incredible milestone: 3 years as a VMware Technical Account Manager (TAM). I’m writing about my experiences from the first 3 months to the first 12 months and on. I hope my experiences can highlight what this role is about to any would-be TAMs reading. First Three Months The first three months of any job are difficult. You are (kind of) expected to: learn everyone’s names in your branch and team, your teams structure, how you fit within the overall business, get a grip on what your job actually is vs.

Quick post today! While deploying a vRealize Log Insight (vRLI) cluster with a VIP using vRealize Suite Lifecycle Manager 8.1, you receive this error: Error Code: LCMVRLICONFIG40091 Error occured while configuring vRLI Integrated Load balancer. {"errorMessage":"Specified IP address is not available. It is already held by another host in the network","errorCode":"LOAD_BALANCER_ERROR","errorDetails":{"errorCode":"com.vmware.loginsight.api.errors.loadbalancer.ip_address_unavailable"}} This is clearly due to an issue with the VIP that has been configured. Check both forward and reverse DNS records of course.