<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic vCLS Simplivity VM Data Access Not Optimized in HPE SimpliVity</title>
    <link>https://community.hpe.com/t5/hpe-simplivity/vcls-simplivity-vm-data-access-not-optimized/m-p/7257275#M5615</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;After rebooting the Simplivity (2-node) system, a warning message appeared on Node 2’s vCLS VM.&lt;BR /&gt;The message reads: &lt;STRONG&gt;“vCLS - vCLS Name: Simplivity VM Data Access Not Optimized.”&lt;/STRONG&gt;&lt;BR /&gt;Is there a way to resolve this issue?&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
    <pubDate>Tue, 21 Oct 2025 06:13:14 GMT</pubDate>
    <dc:creator>jilee</dc:creator>
    <dc:date>2025-10-21T06:13:14Z</dc:date>
    <item>
      <title>vCLS Simplivity VM Data Access Not Optimized</title>
      <link>https://community.hpe.com/t5/hpe-simplivity/vcls-simplivity-vm-data-access-not-optimized/m-p/7257275#M5615</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;After rebooting the Simplivity (2-node) system, a warning message appeared on Node 2’s vCLS VM.&lt;BR /&gt;The message reads: &lt;STRONG&gt;“vCLS - vCLS Name: Simplivity VM Data Access Not Optimized.”&lt;/STRONG&gt;&lt;BR /&gt;Is there a way to resolve this issue?&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Tue, 21 Oct 2025 06:13:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-simplivity/vcls-simplivity-vm-data-access-not-optimized/m-p/7257275#M5615</guid>
      <dc:creator>jilee</dc:creator>
      <dc:date>2025-10-21T06:13:14Z</dc:date>
    </item>
    <item>
      <title>Re: vCLS Simplivity VM Data Access Not Optimized</title>
      <link>https://community.hpe.com/t5/hpe-simplivity/vcls-simplivity-vm-data-access-not-optimized/m-p/7257329#M5616</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.hpe.com/t5/user/viewprofilepage/user-id/2125737"&gt;@jilee&lt;/a&gt;,&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;You can resolve this by ensuring that the vCLS VM is running on the same node where its data resides.&lt;/P&gt;&lt;P&gt;In vCenter, right-click the affected vCLS VM &amp;gt;&amp;gt; Select Migrate &amp;gt; Change compute resource only &amp;gt;&amp;gt; Choose the node where the data is locally hosted &amp;gt;&amp;gt; Complete the migration. You can confirm the “data owner” node by logging into the SimpliVity CLI and using the svt-vm-show command.&lt;/P&gt;&lt;P&gt;Look for the affected vCLS VM and check the Data Access Node and Data Locality fields.&lt;BR /&gt;Use the command: svt-vm-show&lt;/P&gt;&lt;P&gt;To prevent SimpliVity from flagging this in the future:&lt;/P&gt;&lt;P&gt;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.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;A href="https://community.hpe.com/t5/user/ViewProfilePage/user-id/2444047" target="_blank" rel="noopener"&gt;&lt;SPAN class=""&gt;Azr_geek&lt;/SPAN&gt;&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 21 Oct 2025 05:53:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-simplivity/vcls-simplivity-vm-data-access-not-optimized/m-p/7257329#M5616</guid>
      <dc:creator>Azr_geek</dc:creator>
      <dc:date>2025-10-21T05:53:38Z</dc:date>
    </item>
    <item>
      <title>Re: vCLS Simplivity VM Data Access Not Optimized</title>
      <link>https://community.hpe.com/t5/hpe-simplivity/vcls-simplivity-vm-data-access-not-optimized/m-p/7257900#M5619</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.hpe.com/t5/user/viewprofilepage/user-id/2125737"&gt;@jilee&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Yes, this issue is related to VMware’s vSphere Cluster Services (vCLS) VM running on your Simplivity cluster. The warning “Simplivity VM Data Access Not Optimized” means the vCLS VM on Node 2 is not leveraging optimal data locality within the Simplivity infrastructure.&lt;/P&gt;&lt;P&gt;To fix the “Simplivity VM Data Access Not Optimized” warning on the vCLS VM, you may:&lt;/P&gt;&lt;P&gt;1. Migrate the vCLS VM to the local Simplivity datastore on Node 2.&lt;BR /&gt;2. Restart the vCLS VM if needed.&lt;/P&gt;&lt;P&gt;This will optimize its data access and remove the warning.&lt;/P&gt;&lt;P&gt;If the warning still stays, ensure DRS is enabled and functioning correctly, as it helps maintain optimal VM placement. Also, avoid deleting vCLS VMs, as they are essential for cluster operations.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Sanika.&lt;/P&gt;&lt;P&gt;If you feel this was helpful, please click the KUDOS thumb below. Also consider marking this as an "Accepted Solution", if the post has helped to solve your issue.&lt;BR /&gt;&lt;BR /&gt;&lt;EM&gt;Thank You!&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;I work with HPE but opinions expressed here are mine.&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&lt;A href="https://support.hpe.com/connect/s/search?language=en_US#t=Videos&amp;amp;sort=%40hpescuniversaldate%20descending&amp;amp;layout=card&amp;amp;numberOfResults=50&amp;amp;f%3A%40kmvideomarketinglabel=%5BTech%20Tips%5D&amp;amp;archive=false" target="_blank"&gt;HPE Tech Tips videos on How To and Troubleshooting topics&lt;/A&gt;&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 31 Oct 2025 03:17:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-simplivity/vcls-simplivity-vm-data-access-not-optimized/m-p/7257900#M5619</guid>
      <dc:creator>Sanika</dc:creator>
      <dc:date>2025-10-31T03:17:28Z</dc:date>
    </item>
  </channel>
</rss>

