<?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 OnCommand Balance 4.2 not mapping Vsphere topology to Netapp controllers in Active IQ Unified Manager Discussions</title>
    <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/OnCommand-Balance-4-2-not-mapping-Vsphere-topology-to-Netapp-controllers/m-p/100145#M17665</link>
    <description>&lt;P&gt;Hi.&lt;/P&gt;&lt;P&gt;We are running an evaluation of Balance 4.2 in our enviroment at the moment.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However the discovery process is not mapping the vsphere datastores to volumes on the Netapp controllers. Is there any way to do this manually?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have seen references in my searches to qtrees being an issue, however this was for version 3.6 and version 4.x apparently fully supports qtrees.&lt;/P&gt;&lt;P&gt;Our datastore mappings look like this: &amp;nbsp;Netappfiler-999:/vol/Volume_name/Qtree_name &amp;nbsp; - there is only one datastore/qtree per volume.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any ideas?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Colin G&lt;/P&gt;</description>
    <pubDate>Thu, 05 Jun 2025 05:10:17 GMT</pubDate>
    <dc:creator>colin_graham</dc:creator>
    <dc:date>2025-06-05T05:10:17Z</dc:date>
    <item>
      <title>OnCommand Balance 4.2 not mapping Vsphere topology to Netapp controllers</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/OnCommand-Balance-4-2-not-mapping-Vsphere-topology-to-Netapp-controllers/m-p/100145#M17665</link>
      <description>&lt;P&gt;Hi.&lt;/P&gt;&lt;P&gt;We are running an evaluation of Balance 4.2 in our enviroment at the moment.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However the discovery process is not mapping the vsphere datastores to volumes on the Netapp controllers. Is there any way to do this manually?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have seen references in my searches to qtrees being an issue, however this was for version 3.6 and version 4.x apparently fully supports qtrees.&lt;/P&gt;&lt;P&gt;Our datastore mappings look like this: &amp;nbsp;Netappfiler-999:/vol/Volume_name/Qtree_name &amp;nbsp; - there is only one datastore/qtree per volume.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any ideas?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Colin G&lt;/P&gt;</description>
      <pubDate>Thu, 05 Jun 2025 05:10:17 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/OnCommand-Balance-4-2-not-mapping-Vsphere-topology-to-Netapp-controllers/m-p/100145#M17665</guid>
      <dc:creator>colin_graham</dc:creator>
      <dc:date>2025-06-05T05:10:17Z</dc:date>
    </item>
    <item>
      <title>Re: OnCommand Balance 4.2 not mapping Vsphere topology to Netapp controllers</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/OnCommand-Balance-4-2-not-mapping-Vsphere-topology-to-Netapp-controllers/m-p/100291#M17698</link>
      <description>&lt;P&gt;Just to answer my own question... Its working now!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It was traced back to Vsphere using dns to mount datastores on the controllers.. once i added the correct dns suffix's into Balance, it started to work, even though Balance cant actually get to the storage networks.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ta&lt;/P&gt;</description>
      <pubDate>Fri, 06 Feb 2015 09:53:27 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/OnCommand-Balance-4-2-not-mapping-Vsphere-topology-to-Netapp-controllers/m-p/100291#M17698</guid>
      <dc:creator>colin_graham</dc:creator>
      <dc:date>2015-02-06T09:53:27Z</dc:date>
    </item>
  </channel>
</rss>

