When configuring an adapter instance for vSAN, you add credentials for a vCenter Server. In the earlier versions of vRealize Operations , the vSAN solution was installed as part of the vRealize Operations installation. Now, in case of a new installation the vSAN solution is pre-bundled as part of vRealize Operations 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 node on which the vSAN adapter resides. This is applicable when the vSAN version in vSphere is 6.6 or lower.
You must have a vCenter Adapter instance configured and monitoring the same vCenter Server that is used to monitor the vSAN and Storage Devices.
To know how to install the Native Management Packs, see Integrations Page.
Procedure
Results
The adapter is added to the Adapter Instance list and is active.
What to do next
- 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 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)
, verify that the vSAN hierarchy includes the following related