VCF Automation — Page 2

Want to harness the power of SaltStack Config for configuration management without tying it to an existing VMware Aria Automation setup? Deploying SaltStack Config 8.17 as a standalone product via VMware Aria Suite Lifecycle Manager (by VMware by Broadcom) is an excellent solution. This step-by-step guide will walk you through the process, ensuring you can set up a standalone SaltStack environment efficiently. Perfect for IT administrators or DevOps teams, this tutorial makes deployment simple and scalable. ...

In this post, I will cover upgrading my 8.x Aria Automation appliance to version 8.18.1 Patch 1. As a prerequisite, we need to have Aria Suite Lifecycle upgraded to 8.18. Instructions can be found here. Note that the upgrade does not include the latest PSPACK containing the 8.18.1 Patch 1 Aria Automation release. Instructions for obtaining the PSPACK are available in here. Note: Following the VMware by Broadcom Day 2 transition on May 6, 2024, Customer Connect has been migrated to the Broadcom Support. This migration impacts the VMware Aria Suite Lifecycle as follows: All Product Support Packs, along with product and patch binaries, will now need to be downloaded from the Broadcom Support Portal Users must then manually map these into the VMware Aria Suite Lifecycle VMware Aria Suite Lifecycle can be upgraded using “Check Online” method. Product Support Packs are cumulative, incorporating all updates from previous product support packs as well as patches into the latest version. Downloading the Patch Binaries The Aria Automation Patch 1 binaries can be downloaded from here. In my case, it was VMware Aria Automation 8.18.1 .patch file (vrlcm-vra-8.18.1-8.18.1.36859.patch). Once downloaded, LCM supports local mappings. In my case, I uploaded the patch in /data/temp ...

Following the deployment of vIDM which can be found here, deploying VMware Aria Automation (formerly known as vRealize Automation) enhances your VCF environment with powerful self-service provisioning, automated operations, and streamlined infrastructure management. This step-by-step guide will walk you through deploying Aria Automation using VMware Aria Lifecycle Manager in a VCF 5.2.1 environment, integrating it seamlessly with vIDM for Single Sign-On (SSO) and access management. Prerequisites VMware Cloud Foundation (VCF) 5.2.1 Environment: Ensure VCF 5.2.1 is fully set up and operational. Aria Lifecycle Manager (ALCM) Appliance: Make sure Aria Lifecycle Manager is installed and accessible. Identity Management (vIDM): Deployed and configured to allow SSO across VMware products. DNS and Network Configurations: Validated for reachability and FQDN resolution. Step 1: Access Aria Lifecycle Manager Log in to the Aria Lifecycle Manager (ALCM) console with admin credentials. Ensure your ALCM version aligns with VCF 5.2.1, ensuring compatibility. Step 2: Add an Environment in ALCM In ALCM, navigate to Environments and Add New Environment. Input environment details, such as name and description, to organize deployments within the ALCM. Select a Datacenter for the deployment. Click Next. ...

Changing the IP address of a Aria Automation node requires careful planning to avoid service disruption. Here’s a step-by-step guide: 1. Verify Health of vRealize Automation Run: vracli service status Ensure the cluster or node is healthy before proceeding. 2. Set Alternative IP Address vracli network alternative-ip set --dns <DNS_IP1>,<DNS_IP2> <New_IP>/<subnet> <Gateway_IP> ...

In this post, I will cover upgrading my 8.x Aria Automation appliance to version 8.18. As a prerequisite, we need to have VMware Aria Suite Lifecycle upgraded to 8.18. Instructions can be found here. Note: Following the VMware by Broadcom Day 2 transition on May 6, 2024, Customer Connect has been migrated to the Broadcom Support. This migration impacts the VMware Aria Suite Lifecycle as follows: All Product Support Packs, along with product and patch binaries, will now need to be downloaded from the Broadcom Support Portal Users must then manually map these into the VMware Aria Suite Lifecycle VMware Aria Suite Lifecycle can be upgraded using “Check Online” method. Product Support Packs are cumulative, incorporating all updates from previous product support packs as well as patches into the latest version. Downloading and Mapping the Binaries The Aria Automation binaries can be downloaded from here. In my case, it was VMware Aria Automation 8.18.0 Update Repository (Prelude_VA-8.18.0.35770-24024333-updaterepo.iso). Once downloaded, LCM supports local or NFS mappings. In my case, I uploaded the binary in /data ...

Upgrading Aria Automation (formerly known as vRealize Automation, vRA) is crucial for maintaining the efficiency, security, and compatibility of your automation tasks. For environments without VMware Aria Suite Lifecycle, you can still perform the upgrade using the vracli command-line utility. If your environment does have Lifecycle Manager, I covered upgrading VMware Aria Automation to 8.18 through it in a separate guide. This blog post will guide you through the process of upgrading Aria Automation using two different methods: from a mounted ISO (CD-ROM) and from an online update repository URL. ...

Upgrading Aria Automation (formerly known as vRealize Automation, vRA) is crucial for maintaining the efficiency, security, and compatibility of your automation tasks. For environments without VMware Aria Suite Lifecycle, you can still perform the upgrade using the vracli command-line utility. This blog post will guide you through the process of upgrading Aria Automation using two different methods: from a mounted ISO (CD-ROM) and from an online update repository URL. ...

Introduction Automation in VMware environments enhances efficiency, reduces human error, and improves the consistency of operations. Aria Automation (formerly vRealize Automation) is a powerful tool designed to automate processes in your VMware infrastructure. However, to fully leverage its capabilities, Aria Automation requires specific permissions in vCenter. This blog post will guide you through creating a custom role in vCenter with all necessary permissions for the Aria Automation service account. Before You Begin Prerequisites ...

While trying to upgrade my SaltStack Config environment to 8.16.2 I encountered Error Code: LCMVSSC10013 in VMware Aria Suite Lifecycle. The error details: Error Code: LCMVSSC10013 Failed to import VMware Aria Automation Config. Exception occurred while importing VMware Aria Automation Config host. Exception message: Import of VMware Aria Automation Config failed for tenant Standalone vRASSC com.vmware.vrealize.lcm.vsse.common.exception.VsscImportFailureException: Import of VMware Aria Automation Config failed for tenant Standalone vRASSC at com.vmware.vrealize.lcm.vsse.core.task.VsscImportTask.execute(VsscImportTask.java:185) at com.vmware.vrealize.lcm.platform.automata.service.Task.retry(Task.java:158) at com.vmware.vrealize.lcm.automata.core.TaskThread.run(TaskThread.java:60) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.base/java.lang.Thread.run(Unknown Source) Caused by: java.lang.RuntimeException: Cannot execute ssh commands. Exception encountered : Session.connect: java.security.spec.InvalidKeySpecException: key spec not recognized at com.vmware.vrealize.lcm.util.SshUtils.execute(SshUtils.java:721) at com.vmware.vrealize.lcm.util.SshUtils.runCommand(SshUtils.java:532) at com.vmware.vrealize.lcm.util.SshUtils.runCommand(SshUtils.java:516) at com.vmware.vrealize.lcm.util.SshUtils.runCommand(SshUtils.java:628) at com.vmware.vrealize.lcm.vsse.core.task.VsscImportTask.fetchFipsStatus(VsscImportTask.java:342) at com.vmware.vrealize.lcm.vsse.core.task.VsscImportTask.getProductDetails(VsscImportTask.java:260) at com.vmware.vrealize.lcm.vsse.core.task.VsscImportTask.execute(VsscImportTask.java:158) ... 5 more Caused by: java.lang.RuntimeException: Cannot create session for ssh://root@ssc-01a.corp.local at com.vmware.vrealize.lcm.util.SessionHolder.newSession(SessionHolder.java:57) at com.vmware.vrealize.lcm.util.SessionHolder.<init>(SessionHolder.java:37) at com.vmware.vrealize.lcm.util.SshUtils.execute(SshUtils.java:663) ... 11 more Caused by: com.jcraft.jsch.JSchException: Session.connect: java.security.spec.InvalidKeySpecException: key spec not recognized at com.jcraft.jsch.Session.connect(Session.java:550) at com.vmware.vrealize.lcm.util.SessionHolder.newSession(SessionHolder.java:53) ... 13 more Caused by: java.security.spec.InvalidKeySpecException: key spec not recognized at org.bouncycastle.jcajce.provider.asymmetric.util.BaseKeyFactorySpi.engineGeneratePublic(Unknown Source) at org.bouncycastle.jcajce.provider.asymmetric.edec.KeyFactorySpi.engineGeneratePublic(KeyFactorySpi.java:212) at java.base/java.security.KeyFactory.generatePublic(Unknown Source) at com.jcraft.jsch.jce.XDH.getSecret(XDH.java:71) at com.jcraft.jsch.DHXEC.next(DHXEC.java:134) at com.jcraft.jsch.Session.connect(Session.java:328) ... 14 more To get around it I had to enable FIPS mode in Aria Suite Lifecycle under Lifecycle Operations -> Settings -> Tips Mode Compliance -> check the enabled box -> Click Update ...

In this post I will go over upgrading my 8.x SSC appliance to 8.16.2. As a pre requirement we do need to have VMware Aria Suite Lifecycle upgraded to 8.16. Instructions can be found here. The upgrade does not include the latest PSPACK that contains the 8.16.2 Aria Automation Config release. Instructions to get the PSPACK can be found on my other blog post here. Downloading the 8.16.2 Binaries To get started we can go to VMware Aria Suite Lifecycle -> Lifecycle Operations -> Settings -> Binary Mapping. (If you haven’t added your My VMware credentials you will need to do that first by going to VMware Aria Suite Lifecycle -> Lifecycle Operations -> Settings -> My VMware) ...