<?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 root aggr and DFM in Network and Storage Protocols</title>
    <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/root-aggr-and-DFM/m-p/38562#M3543</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Provisioning manager has &lt;STRONG&gt;no rule of not selecting root&lt;/STRONG&gt; aggr (aggr0) for provisioning, if the required conditions are met could select it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now for your case, Free space is not the only condition needed for provisioning, its should meet all conditions of your policy, your aggr overcommitment %, licenses, etc. If both your aggr are shown as&amp;nbsp; RED crossed, try the &lt;STRONG&gt;automatic resource selection radio button&lt;/STRONG&gt; at the provisioning page and go to the next step. The next step will fail and will exactly point out the reason for Provisioning Manager (or DFM) not selecting any of the 2 aggrs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you paste this dry-run result( copy to clipboard and let us know)? With that the real cause can be pointed out.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Warm regards,&lt;/P&gt;&lt;P&gt;Abhishek&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 20 Jun 2011 14:15:31 GMT</pubDate>
    <dc:creator>sinhaa</dc:creator>
    <dc:date>2011-06-20T14:15:31Z</dc:date>
    <item>
      <title>root aggr and DFM</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/root-aggr-and-DFM/m-p/38558#M3542</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One of my customer is in the process of integrating DFM to thier exsiting filer environment.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;They have 2 aggrs, when tried to provision a NFS share always one of the Aggr is coming with a RED Corss on it (Basically DFM can not use it).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Both the Aggrs are having free space and is having provisioned NFS and iSCSI data sets&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Only difference is the Aggr skipped is the root aggregate,since I do not have much exposure to DFM I am checking with you if that is the case.&lt;/P&gt;&lt;P&gt;(ie DFM by default will not use root aggregate for provisioning any new volumes/LUNs ?)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:52:43 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/root-aggr-and-DFM/m-p/38558#M3542</guid>
      <dc:creator>baijulal</dc:creator>
      <dc:date>2025-06-05T06:52:43Z</dc:date>
    </item>
    <item>
      <title>root aggr and DFM</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/root-aggr-and-DFM/m-p/38562#M3543</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Provisioning manager has &lt;STRONG&gt;no rule of not selecting root&lt;/STRONG&gt; aggr (aggr0) for provisioning, if the required conditions are met could select it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now for your case, Free space is not the only condition needed for provisioning, its should meet all conditions of your policy, your aggr overcommitment %, licenses, etc. If both your aggr are shown as&amp;nbsp; RED crossed, try the &lt;STRONG&gt;automatic resource selection radio button&lt;/STRONG&gt; at the provisioning page and go to the next step. The next step will fail and will exactly point out the reason for Provisioning Manager (or DFM) not selecting any of the 2 aggrs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you paste this dry-run result( copy to clipboard and let us know)? With that the real cause can be pointed out.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Warm regards,&lt;/P&gt;&lt;P&gt;Abhishek&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 20 Jun 2011 14:15:31 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/root-aggr-and-DFM/m-p/38562#M3543</guid>
      <dc:creator>sinhaa</dc:creator>
      <dc:date>2011-06-20T14:15:31Z</dc:date>
    </item>
  </channel>
</rss>

