vCLS Simplivity VM Data Access Not Optimized

[jilee]

Hello,

After rebooting the Simplivity (2-node) system, a warning message appeared on Node 2’s vCLS VM.
The message reads: “vCLS - vCLS Name: Simplivity VM Data Access Not Optimized.”
Is there a way to resolve this issue?

Thanks.

[Azr_geek]

Hello @jilee,

You can resolve this by ensuring that the vCLS VM is running on the same node where its data resides.

In vCenter, right-click the affected vCLS VM >> Select Migrate > Change compute resource only >> Choose the node where the data is locally hosted >> Complete the migration. You can confirm the “data owner” node by logging into the SimpliVity CLI and using the svt-vm-show command.

Look for the affected vCLS VM and check the Data Access Node and Data Locality fields.
Use the command: svt-vm-show

To prevent SimpliVity from flagging this in the future:

Set a VM-to-Host affinity rule for the vCLS VM to prefer the correct node. Be cautious: vCLS VMs are managed by vCenter, so manual rules should not conflict with automated DRS behavior.

Regards,
Azr_geek