<?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 Re: How to optimize FC auto resolution in Active IQ Unified Manager Discussions</title>
    <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/How-to-optimize-FC-auto-resolution/m-p/147072#M26761</link>
    <description>&lt;P&gt;Hi there!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Certainly sounds like you have a very large environment. Normal course of action would be to create a case complaining of the long time it takes to load that aspect of the UI. There may not be an immediate resolution, but your account team can help have the issue escalated to an eventual resolution.&amp;nbsp;Do you have a TAM or SAM from NetApp assigned to your account?&lt;/P&gt;</description>
    <pubDate>Wed, 13 Mar 2019 04:48:18 GMT</pubDate>
    <dc:creator>AlexDawson</dc:creator>
    <dc:date>2019-03-13T04:48:18Z</dc:date>
    <item>
      <title>How to optimize FC auto resolution</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/How-to-optimize-FC-auto-resolution/m-p/147010#M26754</link>
      <description>&lt;P&gt;We have a lot of switches and, unfortunately, a lot of naming conventions used for alias and zones.&lt;/P&gt;
&lt;P&gt;So we created a lot of rules in order to capture all wwns.&lt;/P&gt;
&lt;P&gt;The limit with this is that the Device resolution page need 2-3 minutes to be created.&lt;/P&gt;
&lt;P&gt;With Developper tools I saw this is because a json is created with the report of every rule for all of the wwns ( so about 30000 * 27 rows only for that ).&lt;/P&gt;
&lt;P&gt;Is there a way to check what are the most used rules and optimize them?&lt;/P&gt;
&lt;P&gt;Thanks in advance for the help&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 12:45:13 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/How-to-optimize-FC-auto-resolution/m-p/147010#M26754</guid>
      <dc:creator>Giatherock</dc:creator>
      <dc:date>2025-06-04T12:45:13Z</dc:date>
    </item>
    <item>
      <title>Re: How to optimize FC auto resolution</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/How-to-optimize-FC-auto-resolution/m-p/147072#M26761</link>
      <description>&lt;P&gt;Hi there!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Certainly sounds like you have a very large environment. Normal course of action would be to create a case complaining of the long time it takes to load that aspect of the UI. There may not be an immediate resolution, but your account team can help have the issue escalated to an eventual resolution.&amp;nbsp;Do you have a TAM or SAM from NetApp assigned to your account?&lt;/P&gt;</description>
      <pubDate>Wed, 13 Mar 2019 04:48:18 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/How-to-optimize-FC-auto-resolution/m-p/147072#M26761</guid>
      <dc:creator>AlexDawson</dc:creator>
      <dc:date>2019-03-13T04:48:18Z</dc:date>
    </item>
    <item>
      <title>Re: How to optimize FC auto resolution</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/How-to-optimize-FC-auto-resolution/m-p/147387#M26808</link>
      <description>&lt;P&gt;Hi Alex,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;yes it's true. We have a large environment ( &amp;gt; 16000 ports ) and we have alreay also open a case for that.&lt;/P&gt;
&lt;P&gt;Thanks for your help&lt;/P&gt;</description>
      <pubDate>Fri, 22 Mar 2019 14:56:28 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/How-to-optimize-FC-auto-resolution/m-p/147387#M26808</guid>
      <dc:creator>Giatherock</dc:creator>
      <dc:date>2019-03-22T14:56:28Z</dc:date>
    </item>
  </channel>
</rss>

