When Usage Meter starts metering vSAN associated with a vCenter Server with a version before 7.0, and there is a vSAN cluster with an enabled Stretched Cluster feature, then Usage Meter returns a partial collection error in the Notifications tab in the Usage Meter web application.
The following error is also observed in the /opt/vmware/cloudusagemetering/var/logs/vccol_error.log/vccol_main.log file on the Usage Meter appliance.
<Date> ERROR --- [vCenter collector thread] com.vmware.um.vccollector.VCCollector : VSAN stage raised exception com.sun.xml.ws.fault.ServerSOAPFaultException: Client received SOAP Fault from server: Unable to resolve WSDL method name QuerySharedWitnessCompatibility for namespace name urn:vsan
As a result, no vSAN usage data is collected for the given vCenter Server, and the vSAN units in the usage reports are incorrect.
The reason this error occurs is that the QuerySharedWitnessCompatibility API endpoint does not exist in vCenter Server before version 7.0. This request is used to detect if a vSAN cluster uses a Stretch Cluster or Shared Witness feature.
To be able to collect vSAN usage data, run the following vSAN collection script from Customer Connect at least once a month and raise a support request to our Global Services Support Team. The script needs to be run each month until you upgrade to a newer Usage Meter version.
If you are using a read-only user with which Usage Meter to connect to the vCenter Server with deployed vSAN, you will need to add the Profile-Driven Storage and CNS Searchable roles to that user. These roles are needed by Usage Meter to query vSAN usage data. Information on how to add them, you can find here.
To collect usage data from your vSAN clusters, do the following:
Prerequisites:
Procedure:
systemctl enable sshd
systemctl start sshd
From the local machine where the script is downloaded, copy remotely the script to a directory on the Usage Meter appliance,e.g., /home/usagemeter/.
scp <source-file-path> usagemeter@<ip-address>:<destination-directory>
ssh usagemeter@<um-ip-address>
Go to the directory where the script was copied to, e.g. /home/usagemeter/.
cd /home/usagemeter
Run the script from the directory where the script is located:
python3 collect_vsan_usage.py
When prompted, enter the following details of the vCenter Server on which vSAN is deployed:
The vCenter Server IP address
The vCenter Server ID is taken from the Product ID column in the Usage Meter web application, e.g., ‘21’.
Username and password of the user with which Usage Meter will connect to the vCenter Server.
exit
scp usagemeter@<um-ip-address>:/<source-file-path> <destinaion-local-directory>
systemctl stop sshd
After the reporting month completes and receiving the generated vSAN usage reports from our Global Services Support team, enter the vSAN usage data in your Monthly Billing Order (MBO) in the Commerce Portal. Learn how to edit your MBO here.