VMware End-of-Life Updates

-

As a user of VMware (VMware by Broadcom), it's crucial to stay informed about the latest End of Life (EOL) updates to ensure smooth operations and compliance with platform changes. Here's a rundown of the upcoming EOL dates and actions you need to take:


April 30 EOL Updates:

  • Cloud Partner Navigator and Usage Data Download: The ability to access Cloud Partner Navigator and download any usage data will be discontinued after 11:59 PM PDT on April 30. Make sure to retrieve any necessary data before this date.

  • VMware Cloud Services Provider Transacting Ability: VMware Cloud Services Providers will no longer be able to transact under the VMware Partner Connect Program after April 30. If you're a Cloud Services Provider, ensure that any pending transactions are completed before the deadline.

  • Cloud Services Provider – SaaS Program: The Cloud Services Provider – SaaS Program, formerly known as MSP Program, will reach its EOL on April 30. Take necessary actions to wrap up any ongoing activities related to this program.

  • VMware Partner Connect Portal and VMware Partner Locator: Access to the VMware Partner Connect Portal and VMware Partner Locator will cease after April 30. Plan accordingly and find alternative resources for partner collaboration and networking.


May 31 EOL Updates:

  • Partner Rewards Portal: The Partner Rewards Portal will be reaching its final EOL on May 31. Note that the final claim deadline for this portal is April 15. Ensure that any pending claims are submitted before the deadline.

Additional Information:

VMC/VMCU Credits Redemption: All VMware Cloud (VMC) and VMware Cloud Universal (VMCU) custom-skinned credits must be fully utilized by April 30, 2024. These credits will not be migrated to the new credit portal experience. Any unused credits after April 30 will only apply to available VMCU products going forward. Work closely with your customers to utilize these credits before the deadline, including generic SPP credits.

Keeping track of these EOL updates and taking timely action is essential to ensure a seamless transition and continued support from VMware. Stay vigilant and proactively address any pending tasks to avoid disruptions in your operations.

Remember, staying informed is the key to staying ahead in the ever-evolving landscape of technology.

Comments

Post a Comment

Popular posts from this blog

All shared datastores failed on the host

-
  Sometimes post creating a new cluster or after re-configuring the existing cluster you might get an error on ESXi “All shared datastores failed on the host”  this can happen to you very often if you are running on HPE StoreVirtual VSA. Please follow the below steps to fix this error: 1.     At the very onset, Reconfigure the HA for the cluster. Disable and re-enable HA on Cluster Level or Right Click Host and select Reconfigure for vSphere HA. 2.     If the error still persists, then follow the next steps. 3.     Make sure you migrate all the VMs manually on the other host if the DRS is disabled on the cluster. 4.     If you have any VM running on ESXi local Datastore like HPE StoreVirtual Appliance (VSA) or Backup Proxy VM, ensure to gracefully shut them down. (For How to shutdown HPE VSA gracefully follow this KB ) 5.     Now, put the host in Maintenance Mode. 6.     Right Click Host and Remove from Inventory 7.     After the host is removed, Right Click on the cluster and click A
Read more

How to Downgrade a VIB/Driver in ESXi 7

-
Image
  There are two methods to downgrade a VIB or a device driver in ESXi Host. 1.     Uninstall the current or upgraded driver > reboot the host > Install the downgrade driver OR 2.     You may also install the downgrade driver directly using esxcli software vib install command. This will remove the upgraded driver itself. Let's see how to perform downgrades of vib using both methods. You may decide which one you would like to choose. You may also install drivers using Baselines in Lifecycle Manager, which will be covered in later posts. Method 1 : Uninstall the current or upgraded driver > reboot the host > Install the downgrade driver Put the ESXi host in Maintenance Mode. SSH the ESXi host Run this command to uninstall the driver: " esxcli software vib remove -n <vib_name> " Reboot the host Run this command to install the driver: " esxcli software vib install -d /vmfs/volume/datastore/vib.zip "   Reboot the host Run this command to
Read more

Error: "Datastore "XXX" conflicts with an existing datastore"

-
Image
  PROBLEM Recently I tried to upgrade one of my ESXi hosts from version 6.7 to 7.0 using VMware Lifecycle Manager. The upgrade gets stuck at 47%. However, when I take the remote console using iLO, I see the ESXi is already upgraded. The LCM Events and logs show that vCenter is not able to connect to the host.  I tried to connect the Host manually and got the below error: Datastore "XXX" conflicts with an existing datastore in the datacenter that has the same URL "UUID", but it is backed by different physical storage. RESOLUTION 1.     Check if the all the vmhba are visible: Run this command to see all vmhba - esxcfg-scsidevs -a or esxcli storage core adapter list 2.     Check if the vmhba drivers are compatible. In my case smartpqi driver had to be upgraded to latest version. (Microchip-smartpqi_70.4054.2.118-1OEM.700.1.0.15843807_17871815) 3.     Check if the datastore is accessible and visble from ESXi UI or ESXCLI. 4.     Remove the host from
Read more