Search Results

Understanding Creutzfeldt-Jakob Disease (CJD) Creutzfeldt-Jakob Disease (CJD) is a rare and rapidly progressing neurodegenerative condition that primarily affects the brain. It is classified as a prion disease, which means that it is caused by abnormal proteins (prions) that damage brain tissue, leading to severe neurological symptoms. Although CJD is rare, with approximately one to two cases per million people per year worldwide, its effects can be devastating. This blog aims to provide an overview of CJD, including its symptoms, types, diagnosis, and treatment options. What is CJD? CJD belongs to a family of diseases known as prion diseases, which includes other rare conditions like Kuru, fatal familial insomnia, and Gerstmann-Sträussler-Scheinker syndrome. Prions are misfolded proteins that cause a cascade of abnormal folding in healthy proteins in the brain. This leads to cell death and tissue damage, ultimately causing brain shrinkage and spongiform changes, which are characteristic of the disease. Types of CJD There are four main types of CJD: Sporadic CJD (sCJD): This is the most common form, accounting for 85-90% of cases. It usually occurs randomly in people aged 60-65, with no known risk factors or genetic link. Familial or Inherited CJD (fCJD): Caused by a mutation in the PRNP gene, which encodes the prion protein. Makes up 10-15% of CJD cases. Individuals with a family history of CJD or other prion diseases are at higher risk. Acquired CJD: Results from exposure to infectious prions from contaminated medical equipment, organ transplants, or consumption of infected beef (Bovine Spongiform Encephalopathy or “mad cow disease”). While extremely rare, outbreaks of variant CJD (vCJD) have been linked to BSE. Variant CJD (vCJD): Linked to exposure to BSE in cattle. Typically affects younger individuals, and the disease course is longer than other forms of CJD. Symptoms of CJD CJD is characterized by rapid mental deterioration, leading to severe disability and death within a year in most cases. Common symptoms include: Rapidly progressive dementia Memory loss and confusion Personality changes Hallucinations Muscle stiffness or twitching Difficulty with coordination and balance Speech and vision problems Eventually, patients enter a coma-like state and often succumb to pneumonia or other infections. Diagnosis of CJD Diagnosing CJD is challenging due to its rarity and similarity to other neurological disorders. Typically, a combination of tests is used, including: Electroencephalogram (EEG): Measures brain wave patterns and can show characteristic changes in CJD. MRI Scans: Can reveal brain abnormalities indicative of CJD. Cerebrospinal Fluid (CSF) Tests: Detects certain proteins that are markers for prion disease. Genetic Testing: For individuals with a family history, genetic tests can identify mutations associated with familial CJD. Treatment and Management Currently, there is no cure for CJD. Treatment focuses on alleviating symptoms and providing supportive care. This may include: Pain relief Medications to reduce muscle spasms Psychological support for patients and families Ensuring a comfortable environment for end-of-life care Researchers are actively exploring new treatments, including drugs that target prions and gene therapies, but these are still in experimental stages. Prevention and Risk Mitigation Preventing CJD is challenging due to its sporadic nature. However, some steps can be taken to reduce the risk of acquired CJD: Implementing strict controls on the use of medical equipment, particularly in neurosurgery, to avoid cross-contamination. Regulating the food supply to prevent exposure to BSE. Genetic counseling for individuals with a family history of CJD. Living with CJD CJD is a devastating disease, not only for the individual but also for their families. The rapid progression and lack of effective treatment options make it particularly hard to cope with. Support groups and counseling can provide emotional and psychological support during this difficult time. Conclusion Creutzfeldt-Jakob Disease is a rare but fatal neurodegenerative disorder caused by prions. Despite its rarity, understanding the disease, its symptoms, and its progression is crucial for healthcare professionals and researchers. While there is currently no cure, ongoing research offers hope for the development of effective treatments in the future. For those looking for more information or support, organizations such as the CJD Foundation and local prion disease centers can provide valuable resources and guidance.

VMware Aria Suite Lifecycle 8.18.0 Product Support Pack 2 is now released. This Product Support Pack provides support for installing or upgrade of VMware Aria Operations 8.18.1 Download Link https://support.broadcom.com/web/ecx/solutiondetails?patchId=5527 Release Notes https://docs.vmware.com/en/VMware-Aria-Suite-Lifecycle/8.18/rn/vmware-aria-suite-lifecycle-818-product-support-pack-release-notes/index.html

There's always an ask to me on what versions are supported with a specific product support pack. That's the reason i've written this blog which has screenshots of every product support pack released for last few versions of VMware Aria Suite Lifecycle What is a Product Support Pack? In VMware Aria Suite Lifecycle, a Product Support Pack is a software package that updates an existing product support policy to incorporate support for new releases of VMware Aria suite of products. Here's a link to another blog i have written which explains why you need a Product Support Pack: https://www.arunnukula.com/post/why-do-i-need-product-support-packs-let-s-learn VMware Aria Suite Lifecycle 8.18.0 8.18 PSPACK 1 8.18.0 GA VMware Aria Suite Lifecycle 8.16.0 8.16.0 GA VMware Aria Suite Lifecycle 8.14.0 8.14.0 PSPACK 8 8.14.0 PSPACK 7 8.14.0 PSPACK 6 8.14.0 PSPACK 5 8.14.0 PSPACK 4 8.14.0 PSPACK 3 8.14.0 PSPACK 2 8.14.0 PSPACK 1 8.14.0 GA VMware Aria Suite Lifecycle 8.12.0 8.12.0 PSPACK 10 8.12.0 PSPACK 9 8.12.0 PSPACK 8 8.12.0 PSPACK 7 8.12.0 PSPACK 6 8.12.0 PSPACK 5 8.12.0 PSPACK 4 8.12.0 PSPACK 3 8.12.0 PSPACK 2 8.12.0 PSPACK 1 8.12.0 GA

This option is only available in a non-VCF aware VMware Aria Suite Lifecycle Good News The online upgrade of VMware Aria Suite Lifecycle was affected by changes on Day-2 in May. However, the issue has been resolved and the service is now restored. When Customers are in connected mode, they have the option to select "Check Online" followed by "Check for Upgrade" to verify the presence of a new manifest and confirm the identification of a new upgrade. Subsequently, they can click on "Upgrade" to continue with the workflow. Please note that customers who are using VMware Aria Suite Lifecycle 8.16.0 Patch 1 or PSPACK 4 are advised to install PSPACK 5 for version 8.16.0 in order to restore this feature in the UI

Login into VMware Aria Suite Lifecycle Go to Lifecycle Operations and Settings Click on System Upgrade Select "Check Online" and then click on "Check for Upgrade" It would return stating the new VMware Aria Suite Lifecycle 8.18.0 is available Ensure a snapshot is taken before triggering an upgrade Click on "Upgrade" to begin the upgrade workflow Pre-checks are fine and now the upgrade starts Remember the logs you can monitor Pre-Upgrade & Upgrade Phase /var/log/vmware/capengine/cap-non-lvm-update/worflow.log /var/log/vmware/capenginecap-non-lvm-updateinstaller-<>.log Post Update Phase /var/log/bootstrap/postupdate.log /data/script.log /var/log/vrlcm/vmware_vrlcm.log Services would restart which means it's in postupgrade phase Upgrade is now complete Happy Upgrades

VMware Cloud Foundation 5.2 which comprises of VMware Aria Suite 8.18.0 comes with the following new versions of the products Product Version VMware Aria Suite Lifecycle 8.18.0 VMware Aria Operations 8.18.0 VMware Aria Automation 8.18.0 VMware Aria Operations for Networks 6.13.0 VMware Aria Operations for Logs 8.18.0 VMware Aria Automation Orchestrator 8.18.0 From where can I download the VMware Aria Suite Lifecycle 8.18.0 upgrade package? Click here which would open a browser which will take you to Broadcom Support Portal. Following screen is what you would see VMware Aria Suite Lifecycle 8.18 Easy Installer for Automation and vIDM binary helps you to install VMware Aria Suite Lifecycle , VMware Identity Manager and VMware Aria Automation together The VMware Aria Suite Lifecycle 8.18 Update Repository Archive is the upgrade package specifically designed for VMware Aria Suite Lifecycle 8.18.0. If you are currently using an older version of Suite Lifecycle, you can utilize this package to upgrade to version 8.18.0. VMware Aria Suite Lifecycle 8.18 Easy Installer binary helps you to only install VMware Aria Suite Lifecycle , this does not contain VIDM and Automation binaries This link will take you to the page where you can download all the binaries mentioned above Product Support Packs have been launched to assist with upgrading VMware Aria Suite Lifecycle to version 8.18.0 if you are in VCF Aware Mode If your VMware Aria Suite Lifecycle is in Non-VCF aware mode, then there is no need to apply these product support packs on previous versions of Suite Lifecycle, just download the upgrade repo and then upgrade Policy Screenshot once an upgrade to VMware Aria Suite Lifecycle 8.18.0 is completed PSPACK Information Download Link Release Notes vRealize Suite Lifecycle Manager 8.8.2 PSPACK 11 Download Link Release Notes vRealize Suite Lifecycle Manager 8.10.0 PSPACK 19 Download Link Release Notes VMware Aria Suite Lifecycle 8.12.0 PSPACK 11 Download Link Release Notes VMware Aria Suite Lifecycle 8.14.0 PSPACK 9 Download Link Release Notes VMware Aria Suite Lifecycle 8.16.0 PSPACK 5 Download Link Release Notes

VMware Aria Suite Lifecycle 8.16.0 Product Support Pack 4 is now released This Product Support Pack provides support for VMware Aria Operations 8.17.2 VMware Aria Operations for Logs 8.16.1 Click here for Release Notes Click here for Downloading Product Support Pack 4 After applying VMware Aria Suite Lifecycle 8.16.0 Product Support Pack 4, you would see that the My VMware Options would no longer be available

Goal Upgrade an existing VMware Aria Automation 8.xx.xx to 8.17.0 Pre-Requisites VMware Aria Suite Lifecycle 8.16.0 Product Support Pack 3 binary VMware Aria Automation 8.17.0 Upgrade Repo iso Healthy VMware Aria Automation and VMware Aria Suite Lifecycle Download Product Support Pack Direct Download Link : https://support.broadcom.com/web/ecx/solutiondetails?patchId=5338 or Login to the   Broadcom Support Portal . Select "VMware Cloud Foundation" as the product line. Click on "My Downloads" and choose "VMware Aria Universal" or "VMware Aria Suite" Navigate to Solutions, expand the options, and click on Subscription. A list of patches and Product Support Packs will be displayed. Filter to find the appropriate one and click on it to open the download page for that specific Product Support Pack. The syntax to search for a Product Support Pack is always in the format vrslcm-8.16.0-PSPACKx , where x  is the Product Support Pack number Based on the above information, the file we need is vrlcm-8.16.0-PSPACK3.pspak Download VMware Aria Automation Binary In the same Broadcom Support Portal, click on My Downloads Click on the product VMware Aria Automation Select the version you would like to download The file you would need to download in order to upgrade VMware Aria Automation from older version to 8.17.0 is VMware Aria Automation 8.17.0 Update Repository Prelude_VA-8.17.0.35214-23831516-updaterepo.iso which is around 12.91 GB Upload and Install Product Support Pack I have an existing VMware Aria Suite Lifecycle 8.16.0 GA where there are no Product Support Packs Installed Click on upload to select the product support pack downloaded previously. Then click on IMPORT Once the import process completes , refresh the page and you should now see 8.16.0 Product Support Pack 3 available for installation Before heading towards installation ensure a snapshot is taken Click on APPLY VERSION to start the process of installing the product support pack As you can see the product specifically asks for snapshot conscent whether you have taken it or not. So take it for sure. Submit the request to begin the installation During PSPACK installation, the important logs to monitor are /var/log/vrlcm/patchcli.log 2024-05-14 10:30:36,859 - __main__ - INFO - Metadata: {"patchInfo":{"name":"VMware Aria Suite Lifecycle, version 8.16.0 Pspack 3","summary":"Cumulative pspack bundle for vRealize Suite Lifecycle Manager","description":"This cumulative pspack bundle provides fixes to issues observed with various VMware Aria Suite Lifecycle components. Refer the associated docUrl for more details.","kbUrl":"https:\/\/docs.vmware.com\/en\/VMware-vRealize-Lifecycle-Manager\/8.16.0\/rn\/vRealize-Lifecycle-Manager-816-Pspack-3.html","eulaFile":"","category":"bugfix","urgency":"critical","releaseType":"pspack","releaseDate":1715332131000,"additionaInfo":{}},"metadataId":"vrlcm-8.16.0-PSPACK3","metadataVersion":"1","patchId":"8fe69f85-5fad-421a-864c-c0e134b557a3","patchBundleCreationDate":1715332131,"selfPatch":true,"product":{"productId":"vrlcm","productName":"VMware Aria Suite Lifecycle","productVersion":"8.16.0","supportedVersions":["8.16.0"],"productBuild":"10689094","productPatchBuild":"","additionaInfo":{"patchInstructions":"mkdir -p \/data\/tmp-pspack-81603\/10318114; cp -r /tmp/10318114/VMware-vLCM-Appliance-8.16.0-PSPACK3.pspak \/data\/tmp-pspack-81603\/10318114; cd \/data\/tmp-pspack-81603\/10318114; unzip VMware-vLCM-Appliance-8.16.0-PSPACK3.pspak; unzip lcm_PSPACK_artifacts.zip; cp -r \/tmp\/10318114\/lcm_pspack_metadata.json \/data\/tmp-pspack-81603\/10318114; sh pre_pspack_instructions.sh; sh pspack_instructions.sh \/data\/tmp-pspack-81603\/10318114 8fe69f85-5fad-421a-864c-c0e134b557a3;"},"patchAlreadyApplied":false},"payload":{"productPatchLevel":"PSPACK3","patchPayloadFilename":"VMware-vLCM-Appliance-8.16.0-PSPACK3.pspak","patchPayloadUri":"","patchPayloadSize":398608505,"sha256sum":"67ab99e5a1cf5f93f111865331d46cc6726bdf34a14fdc19608200b4a2cf4215","productMinorLevel":null},"patchFileName":"vrlcm-8.16.0-PSPACK3.pspak","patchSize":0,"patchSha256sum":"","patchRunningCounter":1,"patchStatus":"ACTIVE","patchDownloadStatus":null,"extract":false,"patchCounter":null} 2024-05-14 10:30:36,859 - __main__ - INFO - Patch File: /tmp/10318114//VMware-vLCM-Appliance-8.16.0-PSPACK3.pspak 2024-05-14 10:30:36,859 - __main__ - INFO - metadata after parsing : 2024-05-14 10:30:36,860 - __main__ - INFO - patch instructions:mkdir -p /data/tmp-pspack-81603/10318114; cp -r /tmp/10318114/VMware-vLCM-Appliance-8.16.0-PSPACK3.pspak /data/tmp-pspack-81603/10318114; cd /data/tmp-pspack-81603/10318114; unzip VMware-vLCM-Appliance-8.16.0-PSPACK3.pspak; unzip lcm_PSPACK_artifacts.zip; cp -r /tmp/10318114/lcm_pspack_metadata.json /data/tmp-pspack-81603/10318114; sh pre_pspack_instructions.sh; sh pspack_instructions.sh /data/tmp-pspack-81603/10318114 8fe69f85-5fad-421a-864c-c0e134b557a3; 2024-05-14 10:30:36,860 - __main__ - INFO - installing patch ... Archive: VMware-vLCM-Appliance-8.16.0-PSPACK3.pspak extracting: lcm_PSPACK_artifacts.zip Archive: lcm_PSPACK_artifacts.zip creating: os/ inflating: vmlcm-service-gui-8.16.0-SNAPSHOT.jar inflating: vmlcm-service-8.16.0-SNAPSHOT.jar inflating: vmware-service-configuration.jar extracting: blackstone.zip inflating: APUAT-8.5.0.18176777.pak inflating: pre_pspack_instructions.sh inflating: pspack_instructions.sh inflating: policy.json inflating: post_patch_instructions.sh inflating: dev-build-upgrade.sh inflating: patchcli.py inflating: patchcliproxy inflating: vlcm-support inflating: vrlcm-server.service 2024-05-14_10:30:42 Pre Product Support Pack vRSLCM 2024-05-14_10:30:42 Cleaning backups from old location... 2024-05-14_10:30:42 Cleaning previous backups... 2024-05-14_10:30:42 Creating new backup file... 2024-05-14_10:30:43 Backup done. 2024-05-14_10:30:43 Copy script to /var/lib/vrlcm 2024-05-14 10:30:49,933 - __main__ - INFO - patch installation process ended. 2024-05-14 10:30:49,933 - __main__ - INFO - patch installation completed. /var/log/vrlcm/bootstrap.log 2024-05-14 10:31:55,251 __main__ - INFO:/var/lib/vrlcm 2024-05-14 10:31:55,251 __main__ - INFO:file removed /var/lib/vrlcm/final/dlfRepo/dlfRepo.zip 2024-05-14 10:31:55,251 __main__ - INFO:zipdir operation 2024-05-14 10:31:55,251 __main__ - INFO:abs_src /var/lib/vrlcm/final/dlfRepo 2024-05-14 10:31:55,252 __main__ - INFO:Adding file to Zip dlfRepo/vssc/8.16.0/dlf/license-vac-80-e9-suite-vrealizeflex-c3-201907.dlf 2024-05-14 10:31:55,252 __main__ - INFO:Adding file to Zip dlfRepo/vssc/8.16.0/dlf/license-vac-80-e5-suite-vrealize-c2-201807.dlf * * * * 2024-05-14 10:35:35,402 __main__ - INFO:delete call is success:http://localhost:8080/lcm/dbservice/api/ischema/properties/webPassword 2024-05-14 10:35:35,415 __main__ - INFO:delete call is success:http://localhost:8080/lcm/dbservice/api/ischema/properties/monitorvRNIWithvROps 2024-05-14 10:35:35,427 __main__ - INFO:delete call is success:http://localhost:8080/lcm/dbservice/api/ischema/properties/monitorvRAWithvROps 2024-05-14 10:35:35,427 __main__ - INFO:file removed /var/lib/vrlcm/final/dlfRepo/dlfRepo.zip 2024-05-14 10:35:35,428 __main__ - INFO:Bootstrap is exit witout any error 2024-05-14 10:35:35,428 __main__ - INFO:schedular api is called /lcm/bootstrap/api/initialize 2024-05-14 10:35:35,515 __main__ - INFO:Response: 2024-05-14 10:35:35,515 __main__ - INFO:Post call is sucessfull url: http://localhost:8080/lcm/bootstrap/api/initialize 2024-05-14 10:35:35,515 __main__ - INFO:lcm schedular started 2024-05-14 10:35:35,515 __main__ - INFO:Error: /tmp/dlfRepo - No such file or directory. 2024-05-14 10:35:35,515 __main__ - INFO:Update Association State Machine is Invoked 2024-05-14 10:35:35,560 __main__ - INFO:Response: 2024-05-14 10:35:35,560 __main__ - INFO:Post call is sucessfull url: http://localhost:8080/lcm/request/api/requests 2024-05-14 10:35:35,560 __main__ - INFO:vmid: eda05d69-967d-4af0-8b80-dd229e720aee 2024-05-14 10:35:35,560 __main__ - INFO:Update License Request:: http://localhost:8080/lcm/request/api/requests/eda05d69-967d-4af0-8b80-dd229e720aee 2024-05-14 10:35:35,586 __main__ - INFO:Response: 2024-05-14 10:35:35,586 __main__ - INFO:Get call is successful url: http://localhost:8080/lcm/request/api/requests/eda05d69-967d-4af0-8b80-dd229e720aee 2024-05-14 10:35:35,587 __main__ - INFO:Update License association request is INPROGRESS 2024-05-14 10:35:35,587 __main__ - INFO:retrying--- Wait for 10 seconds. count: 1 2024-05-14 10:35:45,818 __main__ - INFO:Response: 2024-05-14 10:35:45,818 __main__ - INFO:Get call is successful url: http://localhost:8080/lcm/request/api/requests/eda05d69-967d-4af0-8b80-dd229e720aee 2024-05-14 10:35:45,818 __main__ - INFO:Update License association request COMPLETED 2024-05-14 10:35:45,818 __main__ - INFO:Request either FAILED or is SUCCESS. 2024-05-14 10:35:45,819 __main__ - INFO:file removed /etc/triggerLicenseUpdate 2024-05-14 10:35:45,819 __main__ - INFO:file removed /var/lib/vrlcm/INPROGRESS 2024-05-14 10:35:45,819 __main__ - INFO:Creating SUCCESS file... 2024-05-14 10:35:45,819 __main__ - INFO:SUCCESS file already created... 2024-05-14 10:35:45,819 __main__ - INFO:sucess api count: 3245 failed api count: 0 Above snippets are a success indicators and wait for the services to come back During this process there would be restart of services Once the service is back online, you can see that the product support pack is already installed and we can now map the product binary and we are good to go If you see the policy 8.17.0 version if Automation is present which means either i can install new automation deployment of this version or upgrade an existing old version to automation to this version VMware Aria Automation Upgrade Binary Mapping Downloaded VMware Aria Automation 8.17.0 Upgrade Binary should be mapped in VMware Aria Suite Lifecycle Go to VMware Aria Suite Lifecycle , click on Lifecycle Operations, then browse to SETTINGS and click on Binary Mapping Click on Add Binaries Select Local as i have uploaded to the Suite Lifecycle VA. To upload it to VA, use WINSCP or a FILEZILLA and then copy it to /data folder Select the Binary after it's discovered Then click on ADD The Product Binary Mapping would begin To understand what happens when a product binary is mapped, review this blog post Once the task is completed. Now we are all set to upgrade our existing VMware Aria Automation to 8.17.0 VMware Aria Automation Upgrade Flow ( WORK IN PROGRESS) Ensure Upgrade Binary is mapped You may now see that the upgrade is available on my Automation instance Once you click on upgrade, click on "TRIGGER INVENTORY SYNC" Ensure this completes successfully Inventory Sync is now complete Let's now begin the upgrade. Click on "PROCEED" to start the upgrade flow The repository is already populated Click on NEXT to select Snapshot related options I have selected to Retain the Snapshot taken during upgrade Revert it automatically when a failure occurs , ensuring the application returns to it previous state A log bundle is always collected before it's reverted If GS asks this bundle, go ahead and download it There's a hardware requirement conscent and Run Prechecks Prechecks Succceed and then go ahead with upgrade submission Submit the request to trigger the upgrade Follow the blog which clearly explains what happens in an automation upgrade and what log files to be monitored It is expected to stay on this step for a while as the rpm's are being staged from lcm to automation appliances Upgrade is now completed Just took 1 hour and 8 minutes for a cluster based upgrade This concludes this comprehensive upgrade blog. Hope this helps.

Download VMware Aria Suite Lifecycle Login into Broadcom Support Portal Once you have logged in, select VMware Cloud Foundation Go to MY DOWNLOADS, you would need select the product you wish to download. In this example i would like to download VMware Aria Suite Lifecycle and it's product support packs Select VMware Aria Universal and then click on VMware Aria Universal Enterprise Then click on the Subscription Click on View Group next to VMware Aria Suite Lifecycle Click on the cloud icon to download the binary Product Support Packs and Patches Downloads For downloading Product Support Packs and Patches released for all VMware Aria Products which are wrapped with Suite Lifecycle wrapper, select VMware Aria Universal Click on Solutions , next to the products Then expand enterprise plus and then click on SUBSCRIPTION You would see all patches and product support packs Search for appropriate product support pack or patch and then download it

There's no need to panic when you see this precheck failure VMware Aria Automation needs extra bit of memory compared to previous versions for Medium sized nodes. This will only be seen on Medium sized appliances and not for Extra Large sized appliances. Keep this in mind. The new requirement is 54 GB That's what is stated in the precheck failure What should you do? Power Off VMware Aria Automation using Day-2 action available on the product Delete any snapshots available on the VMware Aria Automation appliances, as you cannot increase the memory to the desired value if they are present Once snapshots are deleted, go ahead and increase the value to the desired 54 GB on all of the appliances (1 applinace if it is a standard deployment, 3 if it is a clustered deployment) Once the appliances are reconfigured, now power them back on using Day-2 action in VMware Aria Suite Lifecycle for VMware Aria Automation Wait for the task to complete. Once done, now the precheck should succeed and then your allowed to upgrade to VMware Aria Automation 8.16.2 Another option is to perform a vertical scale-up, but that would only give you an option to choose extra large sizing which would be way more than you need.

Deploying VMware Aria Operations for Networks through VMware Aria Suite Lifecycle is easy VMware Aria provides the IT Managers or Cloud admin resources to focus on business-critical initiatives, while improving time to value (TTV), reliability and consistency. VMware’s Aria Suite of Products are great, they provide lot’s of feature and capabilities. Supported Products: VMware Aria Automation VMware Aria Automation Orchestrator VMware Aria Automation Automation Config VMware Aria Operations VMware Aria Operations for Logs VMware Aria Operations for Networks Let's begin this blog where we describe installation of VMware Aria Operations for Networks We begin with "Create Environment" where we give Environment Name Description Choose the "Default Password," which will be automatically highlighted in the product pane for customer convenience, especially for those who prefer not to maintain separate passwords for individual accounts within the product. Datacenter would be the location where you would like to provision the product. If a Datacenter has multiple vCenters you can choose one in the infrastructure pane later If you have deployed vRNI previoulsly and want to use the json exported before in this deployment request you can toggle the button Select the product you would like to install. In this example, we will select "VMware Aria Operations for Networks" Accept "EULA" , End User License Agreement From VMware Aria Suite Lifecycle 8.16.0 onwards, products can be deployed in evaluation mode. So there is no mandatory rule to select a license here. That's why you see "NEXT" option enabled even a license is not mapped. Select the certificate needed for the product Key in all the Infrastructure detail in this pane. vCenter where you would like to deploy to Based on the selection of vCenter, select the cluster you would like to deploy to Select the folder and resource pool Select "Network" Select "Datastore" Select "Disk Mode" Togggle the button, if you woild like to integrate the product being deployed to VMware Identity Manager If you have uploaded the ova to Conent Libarary and would like to use it for deployment, toggle the other option, if not proceed Enter appropriate network information in the next pane Domain Name Domain Search Path DNS Servers Time Sync Mode NTP Servers Here comes the Product Pane Selec the FIPS compliance mode You have already selected certificate before. If you would like to select / change to the new one , you can very well do it here If you would like to create an Affinity / Anti-Affinity rule do so Product Password is already selected to "Default Password" before. If you would like to change you may do it here Check or Uncheck the box if you would like to integrate with VMware Identity Manager Select NTP Servers , if you wanna change anything here Then enter details for components Enter Platform Details IP Address Display Name Node Size Enter Collector Details IP Address Display Name Node Size Click on next to perform a Pre-Check It performs checks for Data Validation Infrastructure Validation VMware Aria Operations for Networks Validations Let's say there is a problem, then you would like to fix and then go ahead with the deployment. Remember, you cannot proceed if the pre-check has failures Once all checks are passed , go ahead and click on next to review summary and then deploy the product Now the product is deployed There are different stages which takes place during product deployment If we go through each stages Check Prerequisites Deploys Platform Node Start VMware Aria Operations for Networks Deployment Validate Deploy Inputs Deploy OVF Power On VM Guest Tools Status check Hostname/IP status check VMware Aria Operations for Networks Post Install Check Check Deployment Status Check Services status Check Reconfiguration status VMware Aria Operations for Networks Init License VMware Aria Operations for Networks Platform License Get License VMware Aria Operations Activate Telemetry Config VMware Aria Operations for Networks Certificate Init Apply VMware Aria Operations for Networks Certificate Change VMware Aria Operations for Networks Password Check VIDM Registered Register VMware Aria Operations for Networks O-Auth client Configure VIDM details Create VIDM user Create VMware Aria Operations for Networks app catalog VIDM Create Web Link App Finish Deploys others platform nodes and collectors VMware Aria Operations for Networks Create Cluster VMware Aria Operations for Networks collect FQDN Update environment details Schedule Notifications Toggle fips mode of VMware Aria Operations for Networks Let's explore Day-2 Actions which are available on the product once deployed Action Description Change Admin Password Provides ability to change password for local account in VMware Aria Operations for Networks called "admin@local" Vertical Scale Up Provides ability to change sizing of the cluster. Selec the nodes which are part of the cluster , select the sizing and some advance settings as needed and submit the request to scale up. Trigger Inventory Sync Fetches latest data of the product and updates Suite Lifecycle's inventory. Recomended during Upgrades , Patches, Vertical Scale-up and Licensing changes Replace Certificate Replaces Certificate on the Product Logs Generate& Download log bundles Add Data Sources Ability to add data sources in VMware Aria Operations for Networks Snapshot Take snapshot on the whole cluster Patches Install Patches when released by the product team. Check the history as well Power Off Powers Off VMware Operations for Networks product in a systematic manner Power On Powers On VMware Operations for Networks product in a systematic manner Toggle FIPS mode compliance Change FIPS mode on and off on the product Change Data Sources Password This is specific to VMware Aria Operations for Networks. Suite Lifecycle provides ability to change the data sources password Add License Provides ability to change license View Compatiblity Matrix Check Interop between all VMware Aria Products Delete Product Remove the deployed product from VMware Aria Suite Lifecycle's environment Update NTP Updates NTP configuration on the product Configure Networks Management Pack If a management pack for VMware Aria Operations for Networks is dowloaded from Marketplace then it can be installed using this option Re-Trust with VMware Identity Manager Fetches VMware Identity Manager certificate and then ensure it's updated in the product Re-register with VMware Identity Manager Perform re-registration of the product, incase there is a broken integration Add Components allows you to add more nodes to an existing cluster of VMware Aria Operations for Netowrks In the product's pane you can add addiitonal platform and collector nodes as per guidelines Hope you have got clarity on what options VMware Aria Suite Lifecycle provides for VMware Aria Operations for Networks

In a very rare scenario, you VMware Aria Suite Lifecycle upgrade might be failing before it even starts to upgrade to the new version. This is applicable for upgrades from 8.12.0 ,8.14.0 or 8.16.0 versions of VMware Aria Suite Lifecycle as we leverage a new platform called CAP, Common Appliance Platform Exception reads as below Reference : /var/log/vmware/capengine/core-engine.log 2024/03/01 15:01:50.652977 workflow_handler.go:168: Starting workflow cap-non-lvm-update 2024/03/01 15:01:50.653043 workflow_handler.go:154: Error in executing request. Error: Operation not allowed in the current state of workflow 2024/03/01 15:01:50.653049 engine.go:127: Failed to execute workflow request. Error: Operation not allowed in the current state of workflow What do i do in this case Take a snapshot of VMware Aria Suite Lifecycle appliance. This is mandatory and cannot be skipped Browse to this location /storage/lifecycle/capengine You would see a file called workflow.db root@vrlcm [ / ]# cd storage/lifecycle/capengine root@vrlcm [ /storage/lifecycle/capengine ]# ls workflow.db root@vrlcm [ /storage/lifecycle/capengine ]# ls -ltrh total 36K -rw-r--r-- 1 root root 36K Mar 2 20:47 workflow.db Check the status of cap-workflow-engnie service systemctl status cap-workflow-engine.service Stop the cap-workflow-engine service systemctl stop cap-workflow-engine.service Remove cap engine service workflow database rm -rf /storage/lifecycle/capengine/workflow.db Restart cap engine service systemctl start cap-workflow-engine.service This will recreate a new workflow.db under the same location ls -l /storage/lifecycle/capengine Check the status of cap engine systemctl status cap-workflow-engine.service Expected Output root@vrlcm.arun.com [ /storage/lifecycle/capengine ]# systemctl status cap-workflow-engine.service * cap-workflow-engine.service - Cap workflow engine Loaded: loaded (/lib/systemd/system/cap-workflow-engine.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2024-03-03 02:22:18 UTC; 41min ago Main PID: 2981 (bash) Tasks: 7 (limit: 5883) Memory: 181.5M CGroup: /system.slice/cap-workflow-engine.service |-2981 /bin/bash -c . /etc/profile; /usr/lib/vmware-capengine/capengine `-3039 /usr/lib/vmware-capengine/capengine Mar 03 02:22:21 vrlcm.arun.com bash[2981]: <94><82> Handlers ............ 10 Threads ............. 2 <94><82> Mar 03 02:22:21 vrlcm.arun.com bash[2981]: <94><82> Prefork ....... Disabled PID .............. 3039 <94><82> Mar 03 02:22:21 vrlcm.arun.com bash[2981]: <94><94><94><80><94><80><94><80><94><80><94><80><94><80><94><80><94><80><94><80><94><80><94><80><94><80><94><80><94><80><94><80><94><80><94><80><94> Mar 03 02:22:21 vrlcm.arun.com bash[2981]: <94><8C><94><80><94><80><94><80><94><80><94><80><94><80><94><80><94><80><94><80><94><80><94><80><94><80><94><80><94><80><94><80><94><80><94><80><94> Mar 03 02:22:21 vrlcm.arun.com bash[2981]: <94><82> Fiber v2.1.0 <94><82> Mar 03 02:22:21 vrlcm.arun.com bash[2981]: <94><82> http:///tmp/capengine.sock: <94><82> Mar 03 02:22:21 vrlcm.arun.com bash[2981]: <94><82> <94><82> Mar 03 02:22:21 vrlcm.arun.com bash[2981]: <94><82> Handlers ............ 10 Threads ............. 2 <94><82> Mar 03 02:22:21 vrlcm.arun.com bash[2981]: <94><82> Prefork ....... Disabled PID .............. 3039 <94><82> Mar 03 02:22:21 vrlcm.arun.com bash[2981]: <94><94><94><80><94><80><94><80>< Start your upgrades again