When configuring an adapter instance for vSAN, you add credentials for a vCenter Server. In the earlier versions of vRealize Operations Manager, the vSAN solution was installed as part of the vRealize Operations Manager installation. Now, in case of a new installation the vSAN solution is pre-bundled as part of vRealize Operations Manager OVF, you must install the vSAN solution separately.

Prerequisites

Only vCenter Server systems that are configured for both the vCenter adapter and the vSAN adapter appear in the inventory tree under the vSAN and Storage Devices. Verify that the vCenter Server that you use to configure the vSAN adapter instance is also configured as a vCenter adapter instance for the VMware vSphere® solution. If not, add a vCenter adapter instance for that vCenter Server.

You must open port 5989 between the host and any vRealize Operations Manager node on which the vSAN adapter resides. This is applicable when the vSAN version in vSphere is 6.6 or lower.

To know how to install the Native Management Packs, see Install Native Management Packs and Add Management Packs.

Procedure

  1. In the vCenter Server text box, enter the FQDN or IP address of the vCenter Server instance to which you are connecting.

    The vCenter Server FQDN or IP address must be reachable from all nodes in the vRealize Operations Manager cluster.

  2. To add credentials on the Manage Solution page, click the plus sign.
    1. In the Credential name text box, enter the name by which you are identifying the configured credentials.
    2. Type the User name and Password for the vCenter Server instance.
    3. Click OK.

    You configured credentials to connect to a vCenter Server instance.

  3. Click Advanced Settings and specify the following values:
    Option Description
    Collectors/Groups

    Determines which vRealize Operations Manager collector is used to manage the adapter processes. If you have only one adapter instance, select Default collector group. If you have multiple collectors in your environment, and you want to distribute the workload to optimize performance, select the collector to manage the adapter processes for this instance.

    Auto Discovery

    Determines whether new objects added to the monitored system are discovered and added to vRealize Operations Manager after the initial configuration of the adapter.

    • If the value is true, vRealize Operations Manager collects information about any new objects that are added to the monitored system after the initial configuration. For example, if you add more hosts and virtual machines, these objects are added during the next collections cycle. This is the default value.
    • If the value is false, vRealize Operations Manager monitors only the objects that are present on the target system when you configure the adapter instance.
    Enable SMART data collection

    When set to true, enables SMART data collection for physical disk devices.

    vCenter ID

    A global unique identifier associated with this vCenter instance (VC UUID).

  4. Click Test Connection to validate the connection with your vCenter Server instance.
  5. Accept the vCenter Server security certificate.
  6. Click Save Settings.

Results

The adapter is added to the Adapter Instance list and is active.

What to do next

To verify that the adapter is configured and collecting data from vSAN objects, wait a few collection cycles, then view application-related data.
  • Inventory. Verify that all the objects related to the vSAN instance are listed. Objects should be in the collecting state and receiving data.
  • Dashboards. Verify that vSAN Capacity Overview, Migrate to vSAN, vSAN Operations Overview, and Troubleshoot vSAN, are added to the default dashboards.

  • Under Environment > vSAN and Storage Devices, verify that the vSAN hierarchy includes the following related vCenter Server system objects:
    • vSAN World
    • Cache Disk
    • Capacity Disk
    • vSAN-enabled vCenter Server clusters
    • vSAN Fault Domains (optional)
    • vSAN-enabled Hosts
    • vSAN Datastores
    • vSAN Disk Groups
    • vSAN Datastore related VMs
    • vSAN Witness Hosts (optional)