Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Additional vCenter Server Heartbeat configurations for protecting a local NetApp Virtual Storage Console (1036507)

Symptoms

When a vCenter Server is being protected with vCenter Server Heartbeat and NetApp Virtual Storage Console is installed for NetApp storage interoperability, NetApp Virtual Storage Console may fail to function when the vCenter Server has been failed to the secondary server as the NetApp Virtual Storage Console application data and configuration, by default is not be replicated. The two scenarios where this may occur are:
  • vCenter Server Heartbeat is added to an already installed server running vCenter Server and NetApp Virtual Storage Console
  • NetApp Virtual Storage Console is added to a vCenter Server being protected with vCenter Server Heartbeat

Observation

  • Scenario 1 has, at the time of vCenter Server Heartbeat install, a copy of the NetApp Virtual Storage Console binaries but these are not be updated on the secondary server, so NetApp Virtual Storage Console does not function in terms of the NetApp Virtual Storage Console program configuration differing between server pairs

  • Scenario 2 leaves the secondary server with missing NetApp Virtual Storage Console binaries that prevents NetApp Virtual Storage Console to start when vCenter Server is failed to the secondary server

Resolution

If you experience these symptoms, you may have a fully functional vCenter Server but limited functionality in NetApp Virtual Storage Console. That is, NetApp Virtual Storage Console only operates on the primary server.
  • NetApp Virtual Storage Console services by default are not monitored or protected with recovery options
  • NetApp Virtual Storage Console application data and configuration files by default are not synchronized to the secondary server

This leaves an inconsistent NetApp Virtual Storage Console application within the vCenter Server Heartbeat server pair.

  • NetApp Virtual Storage Console provides its own services to the vSphere Clients
  • NetApp Virtual Storage Console stores its data in the <ProgramFiles>\NetApp\Virtual Storage Console
  • NetApp Virtual Storage Console installs one service, NetApp vSphere Plugin Framework (NVPF)VMware Mount Manager
  • NetApp Virtual Storage Console stores information in the registry under these keys:

    HKEY_LOCAL_MACHINE\Software\NetApp\Virtual Storage Console\
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NVPF\

Workaround

When you have confirmed that you have vCenter Server, vCenter Server Heartbeat and NetApp Virtual Storage Console running locally on the same server, you need to:
  • If your environment is described in scenario 1, proceed to the vCenter Server Heartbeat additional configuration steps.
  • If you environment is described in scenario 2 you will need to repeat the install of NetApp Virtual Storage Console but on the secondary server and with the same configuration as used with the primary server before continuing with the vCenter Server Heartbeat additional configuration steps.

vCenter Server Heartbeat additional configuration

To apply additional configuration steps:

  1. Click vCenter Server Heartbeat \ Manage Server and log into the Management GUI.
  2. Click Advanced Configuration.
  3. Click Application > Services.
  4. Click Add.
  5. Select the individual service listed, NetApp vSphere Plugin Framework (NVPF).

    Leave all service configurations to default 'recover service'.

  6. Click Data > Configuration.
  7. Click Add Inclusion Filter.
  8. Navigate to and select <ProgramFiles>\NetApp\Virtual Storage Console.

The vCenter Server Heartbeat now monitors and protect the NetApp Virtual Storage Console services and synchronizes the application data / configuration files so that both servers are able to fully function as vCenter Servers and NetApp Virtual Storage Console Servers.

Note: A remote vSphere Client may need to log out and back in to successfully display the NetApp Virtual Storage Console Plugin. This is because the remote client is being redirected to the target server and reestablishing a connection.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 1 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 1 Ratings
Actions
KB: