Says Tech Discussions

  Hello Techies! Welcome to Says Tech! In this blog, I will show you to handle the ESXi upgrade issue caused by VIBs installed and the procedure to remove them! De scription: During patch remediation from VMware Update Manager or Lifecycle Manager, it aborted the process by throwing some error: The upgrade has VIBs that are missing dependencies. Remove the VIBs or use Image Builder to create a custom upgrade ISO image that contains the missing dependencies, and try to upgrade again . Software or system configuration of host is incompatible. Check scan results for details. Troubleshooting Steps: 1. Check the scan output from "Updates" tab on the target ESXi host 2. SSH to the target ESXi host and run below command and check the mentioned VIBs                 esxcli software vib list 3. Remove the impacted vib by running below command:                     esxcli software vib remove -n <vib-name> 4. Perform a host reboot before running the upgrade again. Enjoy! Thanks, Arv

Hello Techies! Welcome to Says Tech ! In this blog, we will be understand the procedure of managing host's maintenance mode with the help of SSH commands Description: Entering or exiting a host to & from maintenance mode is quite easy task by vSphere Web Client, you just need to right click on the host --> choose whether to enter or exit from the maintenance. Requirement: Sometimes, if web client isn't available or encountered any issue or you have to work on cli or ssh console, then you can use commands to perform this task. Suggestions: You can either use ESXCLI or VIM-CMD to perform operations for entering or exiting host's maintenance mode. Steps Involved: 1. If you are using ESXCLI, then type below command on the SSH console                 For entering into maintenance mode:                          esxcli system maintenanceMode set --enable true               For exiting from maintenance mode:                          esxcli system maintenanceMode set --enable

 Hello Techies! Welcome to Says Tech ! In this blog, we will understand the procedure to migrate any template from one host to another without converting it to a virtual machine. Description: As we know, VMs can be easily migrated to different hosts using vMotion or automated DRS. Whereas, templates do not have option to self migrate or vMotion capabilities. Suggestions: 1. Either you can convert the template to a virtual machine simply by:         Right click on the template --> Convert to a virtual machine --> use vMotion to migrate      Once done, you can convert the vm to a template again. 2.  Use reallocation / cold migration method Steps Involved: Here we will migrate the template from esx-01 to esx-02 1. Navigate to "VM Templates" 2. Determine the datastore for that template by accessing datastore tab on web client 3. After getting the datastore associated info, right click on the template --> Remove from Inventory     4. Navigate to the datastore --> Acces

Hello Techies! My name is Arvind, a knowledge sharer!  I work as a senior technical and management expert at an esteemed organisation. I am holding expertise in various technologies including servers, operating systems, virtualization, infrastructure setup, etc. I believe that sharing our knowledge with each other make it more wider, hence I will be sharing my knowledge on various technologies with the help of these blogs. Please do share the information if you find it suitable for fixing your issues and maintaining the infrastructure! Let's work together! 

  Hello Mates, Sharing the knowledge regarding an issue which I faced during ESXi/Hypervisor upgrade via Nutanix Prism Elements Description: While upgrading ESXi/Hypervisor from Nutanix Upgrade Software console, the prism elements was running pre-upgrade checks. PS: This can work on any stuck task on Nutanix, just apply the flags/entities as per your need!! Issue Occured: Running task stuck at 10% or 30% or at any certain number for long duration. There was no option to abort the task or cancel it via console Resolution worked: 1. Login into any CVM and run progress monitor           progress_monitor_cli --fetchall                              or           progress_monitor_cli -fetchall| egrep "entity_id|entity_type|operation" 2. Take note of the "Entity ID", "Entity Type" & "Operation" 3. You have the above information now, please run below command to delete the active stuck task           progress_monitor_cli --entity_id="entity_id&quo