VMware vSphere

 View Only
  • 1.  Addressing Alerts in vSphere 7 Setup

    Posted May 17, 2024 01:35 PM
    We have a vSphere 7 setup, and our storage solution relies on Cisco HyperFlex.
    Recently, we've encountered some alerts in the RVTool rapport health report. We're keen to understand how to resolve these issues.
    Could you please provide guidance on fixing the alerts?
    I) Vcenter alerts :
    1)Expired trial license message  "there are expired or expiring licenses in your inventory" keep showing in the top banner of vcenter web page even after activating the premuim license 
    2) A2601-SER-100: HX Alarm 'VC datastore name does not match HX datastore name' showing on the summary tab of the cluster
    II) rvtool rapport health tab alerts :
    1) Inconsistent Foldername! VMname = WinServ2019_FreshInstall Foldername = 2601TS01 
    2) In-Memory VM performance improvement possible! Please check documentation
    3) storage error in rvtool 
    "Handled exception for datastore: 800-SER-100-DATA, System.ServiceModel.FaultException: Permission to perform this operation was denied.
    Server stack trace: 
       at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
       at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
       at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) 
    Exception rethrown at [0]: 
       at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
       at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
       at Vim25Api.VimPortType.SearchDatastoreSubFolders_Task(ManagedObjectReference _this, String datastorePath, HostDatastoreBrowserSearchSpec searchSpec)
       at RVTools.VISDK.SearchDatastoreThread(Thread SearchDatastoreFriendlyNames)"
    4) VMware tools are out of date, not running or not installed! 
    5) There are 27 VMs active on this datastore. The threshold value is 16
    and thanks in advance.

  • 2.  RE: Addressing Alerts in vSphere 7 Setup

    Posted May 19, 2024 04:32 AM

    Hi Ibrahim, 

    Cisco Hyperflex is going End of Life soon, so my suggestion is to start planning a transition from it to another converged solution. vSAN probably wont work because it requires all nodes to have the same storage configuration whereas Hx ships with converged nodes and compute nodes. 

    That being said, the expiring licences error can come from having them in your vCenter but not assigned to any hardware. Make sure to check to remove that license if it exists, even if nothing is attached to it. 

    The alarm "A2601-SER-100: HX Alarm 'VC datastore name does not match HX datastore name'" typically indicates a mismatch between the names of datastores as recognized by vCenter (VC) and Cisco HyperFlex (HX). This discrepancy can cause issues in managing and operating the datastores within the cluster.

    1. Identify the Mismatched Datastores:

      • Log in to vCenter and Cisco HyperFlex Connect.
      • Compare the names of the datastores in both interfaces to identify which ones are mismatched.
    2. Rename the Datastores in vCenter:

      • Go to the vSphere Web Client.
      • Navigate to the datastores section.
      • Right-click the mismatched datastore and select "Rename."
      • Enter the correct name as per the HX datastore name.
      • Confirm the changes.
    3. Verify the Changes:

      • Refresh both vCenter and HX Connect interfaces.
      • Ensure that the datastore names now match in both systems.
    4. Clear the Alarm:

      • After renaming, the alarm should automatically clear. If it does not, you may need to manually acknowledge and clear the alarm in vCenter.
    5. Restart Management Agents (if needed):

      • If the alarm persists, you may need to restart the management agents on the ESXi hosts in the cluster.
      • To restart the management agents:
        • SSH into the ESXi host.
        • Run the following commands:
          services.sh restart
        • Or from the ESXi console:
          • Press F2 to customize the system.
          • Login with the root password.
          • Navigate to Restart Management Agents and restart.

    Love for Virtual Infrastructure!

    VCP-DCV 8.x | VCP-DCV 6.x | CompTIA A+, Net+, Sec+, Proj+ | MCSE | MCSA | MCITP |