When Usage Meter starts metering vSAN deployed on vCenter Server version before 6.7 U3, then it returns a partial collection error in the Notifications tab in the Usage Meter web application.
The following error is also seen in the vCenter collector logs located at /opt/vmware/cloudusagemetering/var/logs/vccol_error.log/vccol_main.log in the Usage Meter appliance:
2023-01-25 17:31:49.595 ERROR --- [vCenter collector thread] c.v.u.v.vsan.VsanServiceSession : Failed to query cluster domain-xx for CNS volumes. 2023-02-1507:23:12.167ERROR --- [vCenter collector thread] com.vmware.um.vccollector.VCCollector : VSAN stage raised exception com.sun.xml.ws.fault.ServerSOAPFaultException: Client received SOAP Fault from server: Unknown type (CnsVolumeManager) Please see the server log to find more detail regarding exact cause of the failure.
As a result of this issue, the vSAN usage data for the given vCenter Server is not reported, and the vSAN units in the usage reports are incorrect.
The reason this error occurs is that the CnsVolumeManager API does not exist in vCenter Server before version 6.7 Update 3. This API is used to detect if a vSAN cluster uses the Cloud Native Storage 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 the script to the Usage Meter appliance.
scp <source-file-path> usagemeter@<um-ip-address>:<destination-directory>
ssh usagemeter@<um-ip-address>
Enter the usagemeter password.
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/ /local-destination-directory/
systemctl stop sshd
After the reporting month completes and receiving your vSAN usage reports from our Global Services Support team, enter manually the vSAN usage data in your Monthly Billing Order (MBO) in the Commerce Portal. Learn how to edit your MBO here.