Snapcenter Plugin for VMWare 4.5 incompatible with vCenter 7.0.3
VMWare (Netapp) Tuesday, 12 October 2021 by paul

After upgrading vCenter to 7.0 Update 3 then Snapcenter Plugin for VMware fails to load with the following error:

Error deploying plug-in. org.apache.felix.resolver.reason.ReasonException: Unable to resolve /usr/lib/vmware-vsphere-ui/server/work/tmp/2150534555311644163com.netapp.scvm.webclient-4.5.0.6025788.esa/scvm_webui_service.jar: missing requirement org.apache.aries.subsystem.core.archive.ImportPackageRequirement: namespace=osgi.wiring.package, attributes={}, directives={filter=(&(osgi.wiring.package=org.springframework.web.servlet.view.velocity)(version>=0.0.0)), resolution=mandatory, uses=javax.servlet,javax.servlet.http,org.apache.velocity,org.apache.velocity.app,org.apache.velocity.context,org.apache.velocity.exception,org.apache.velocity.tools.generic,org.springframework.beans,org.springframework.beans.factory,org.springframework.context,org.springframework.ui.velocity,org.springframework.web.context,org.springframework.web.servlet.view}, resource=/usr/lib/vmware-vsphere-ui/server/work/tmp/2150534555311644163com.netapp.scvm.webclient-4.5.0.6025788.esa/scvm_webui_service.jar org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1340) org.apache.felix.resolver.ResolverImpl.doResolve(ResolverImpl.java:433) org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:420) org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:413) org.apache.aries.subsystem.core.internal.SubsystemResource.computeDependencies(SubsystemResource.java:393) org.apache.aries.subsystem.core.internal.SubsystemResource.computeDependencies(SubsystemResource.java:363) org.apache.aries.subsystem.core.internal.SubsystemResource.<init>(SubsystemResource.java:101) org.apache.aries.subsystem.core.internal.SubsystemResource.<init>(SubsystemResource.java:91) org.apache.aries.subsystem.core.internal.InstallAction.run(InstallAction.java:60) org.apache.aries.subsystem.core.internal.InstallAction.run(InstallAction.java:27) java.security.AccessController.doPrivileged(Native Method) org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:677) org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:730) org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:304) org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:299) org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:71) com.vmware.vise.extensionfw.impl.OsgiBundleDeployer$SubsystemInstallerTask.run(OsgiBundleDeployer.java:706) java.lang.Thread.run(Thread.java:748)

This is due to SCV 4.x not yet being compatible with vCenter 7.0 Update 3. It will be compatible in SCV 4.6 which is currently in development.

The fix is to downgrade vCenter or replace some of the plugin files, on the vCenter server, which updated versions available at the following link:

https://kb.netapp.com/Advice_and_Troubleshooting/Data_Protection_and_Security/SnapCenter/After_upgrade_of_vCenter_Server_7.0_update_3_the_SCV_can_not_be_deployed

 

Hardware Health Issue after ESXi 7.0.2 upgrade
VMWare (Hardware Health) Friday, 08 October 2021 by paul

After upgrade ESXi to version 7.0 Update 2 (7.0.2) the server hardware sensors stop reporting their status.

Accessing Monitor -> Hardware Health no longer lists any sensors.

Trying to refresh return an error:

Running the following commands, from the shell, does not return the expected results:

esxcli hardware ipmi sdr list

esxcli hardware ipmi bmc get

It appears that ESXi has stopped being able to communicate with the BMC to query the hardware sensor data.

 

Solution

VMWare support suggested reimaging the affected ESXi host.

I have found that this is unnecessary. Upgrading the UEFI on the servers fixed the issue.

vCenter Update error after upgrade to 7.0.3
VMWare (Lifecycle Manager) Friday, 08 October 2021 by paul

After upgrading vCenter appliance to 7.0 Update 3 (7.0.3) there is an error displayed when accessing the Update tab (Lifecycle Manager) and logged in using a AD account.

According to the VMWare Knowledgebase article below there is currently no fix available but logging into vCenter using a @vsphere.local account allows access:

"Authentication failed, Lifecycle Manager server could not be contacted", Access to Lifecycle Manager fails in vCenter 7.0 Update 3 when logged in with an Active Directory account (85962) - https://kb.vmware.com/s/article/85962

Microsoft Portals
Office 365 (Admin Portal) Thursday, 30 September 2021 by paul

Microsoft Office 365 now has dozens of Administration Portals. Most can be found through https://admin.microsoft.com but some can only be located if you know the URL.

A great community driven project has put together a webpage listing all the known portals and other important URLs. It can be accessed at:

https://msportals.io/

Install VMWare Tools on Debian Linux
VMWare (Linux) Thursday, 02 September 2021 by paul

An easy way to install Open VMWare Tools onto a Debian VM is to run the following command:

apt-get install open-vm-tools

The version of VMWare Tools can then be checked using the following command:

/usr/bin/vmware-toolbox-cmd -v
Page 1 of 90 (451 Articles) << 1 2 3 4 5  Next >>