<?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 VSC woes on vCenter with other storage solutions in VMware Solutions Discussions</title>
    <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/VSC-woes-on-vCenter-with-other-storage-solutions/m-p/148838#M9546</link>
    <description>&lt;P&gt;In my vSphere environment I have a few different clusters with several different storage solutions. One of these is a Cisco Hyperflex cluster, which is a HCI stack with Cisco's acquired Springpath storage. This creates issues for us when using VSC to provision datastores;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;When running the provisioning wizard it will fail at step 2, select storage system&lt;/LI&gt;
&lt;LI&gt;Reviewing the logs with support last year we identified that VSC cannot resolve the IP of a datastore UID&lt;/LI&gt;
&lt;LI&gt;The UID is connected to the Hyperflex datastore&lt;/LI&gt;
&lt;LI&gt;The workaround is adding an IP that resolves to the ID in /etc/hosts file&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;This is a workaround that lets us provision datastores, but I would like a more permanent solution to this bug. Does anyone have any idea on how we can go about this without manual entries in the hosts-file?&lt;/P&gt;</description>
    <pubDate>Wed, 04 Jun 2025 12:28:31 GMT</pubDate>
    <dc:creator>Ernst</dc:creator>
    <dc:date>2025-06-04T12:28:31Z</dc:date>
    <item>
      <title>VSC woes on vCenter with other storage solutions</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/VSC-woes-on-vCenter-with-other-storage-solutions/m-p/148838#M9546</link>
      <description>&lt;P&gt;In my vSphere environment I have a few different clusters with several different storage solutions. One of these is a Cisco Hyperflex cluster, which is a HCI stack with Cisco's acquired Springpath storage. This creates issues for us when using VSC to provision datastores;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;When running the provisioning wizard it will fail at step 2, select storage system&lt;/LI&gt;
&lt;LI&gt;Reviewing the logs with support last year we identified that VSC cannot resolve the IP of a datastore UID&lt;/LI&gt;
&lt;LI&gt;The UID is connected to the Hyperflex datastore&lt;/LI&gt;
&lt;LI&gt;The workaround is adding an IP that resolves to the ID in /etc/hosts file&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;This is a workaround that lets us provision datastores, but I would like a more permanent solution to this bug. Does anyone have any idea on how we can go about this without manual entries in the hosts-file?&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 12:28:31 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/VSC-woes-on-vCenter-with-other-storage-solutions/m-p/148838#M9546</guid>
      <dc:creator>Ernst</dc:creator>
      <dc:date>2025-06-04T12:28:31Z</dc:date>
    </item>
  </channel>
</rss>

