<?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: option interface.blocked.mgmt_data_traffic in Network and Storage Protocols</title>
    <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/option-interface-blocked-mgmt-data-traffic/m-p/63956#M5803</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Will this also block/restrict e0M from registering to DNS if the option dns.update.enable secure is set? I'm trying to keep the e0M interface from dynamically registering the hostname.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 15 Jun 2012 19:19:56 GMT</pubDate>
    <dc:creator>Andre_Clark</dc:creator>
    <dc:date>2012-06-15T19:19:56Z</dc:date>
    <item>
      <title>option interface.blocked.mgmt_data_traffic</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/option-interface-blocked-mgmt-data-traffic/m-p/63944#M5801</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Fellow Toasters,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can't seem to find any document describing the option interface.blocked.mgmt_data_traffic (found e.g. in Data ONTAP 7.3.6P2, default value: off). Google and now.netapp.com search did not return a single hit.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kindest regards&lt;/P&gt;&lt;P&gt;Peter&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:33:56 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/option-interface-blocked-mgmt-data-traffic/m-p/63944#M5801</guid>
      <dc:creator>pwo</dc:creator>
      <dc:date>2025-06-05T06:33:56Z</dc:date>
    </item>
    <item>
      <title>Re: option interface.blocked.mgmt_data_traffic</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/option-interface-blocked-mgmt-data-traffic/m-p/63948#M5802</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN class="text"&gt;The option &lt;/SPAN&gt;interface.blocked.mgmt_data_traffic&lt;SPAN class="text"&gt; &lt;/SPAN&gt;&lt;SPAN class="text"&gt;controls the protocol filter for dedicated management ports, such as e0M on many platforms (not all platforms have a dedicated &lt;/SPAN&gt;&lt;SPAN class="text"&gt;management &lt;/SPAN&gt;&lt;SPAN class="text"&gt;port). If the option is set to on (the default for &lt;STRONG&gt;new &lt;/STRONG&gt;installs), then NDMP, NFS, CIFS, iSCSI and the SNAP* family of data protocols will be blocked by the dedicated &lt;/SPAN&gt;&lt;SPAN class="text"&gt;management &lt;/SPAN&gt;&lt;SPAN class="text"&gt;port. "On" is the &lt;STRONG&gt;recommended &lt;/STRONG&gt;setting because a dedicated &lt;/SPAN&gt;&lt;SPAN class="text"&gt;management &lt;/SPAN&gt;&lt;SPAN class="text"&gt;port is a low-bandwidth port that does not support jumbo frames, vlans or ifgrps. If a dedicated &lt;/SPAN&gt;&lt;SPAN class="text"&gt;management &lt;/SPAN&gt;&lt;SPAN class="text"&gt;port is used for data traffic, it can hide misconfigurations that might lead to serious loss of filer throughput. A dedicated &lt;/SPAN&gt;&lt;SPAN class="text"&gt;management &lt;/SPAN&gt;&lt;SPAN class="text"&gt;port should only be configured with addresses that are on isolated management-only subnets.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 25 Feb 2012 13:09:34 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/option-interface-blocked-mgmt-data-traffic/m-p/63948#M5802</guid>
      <dc:creator>pwo</dc:creator>
      <dc:date>2012-02-25T13:09:34Z</dc:date>
    </item>
    <item>
      <title>Re: option interface.blocked.mgmt_data_traffic</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/option-interface-blocked-mgmt-data-traffic/m-p/63956#M5803</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Will this also block/restrict e0M from registering to DNS if the option dns.update.enable secure is set? I'm trying to keep the e0M interface from dynamically registering the hostname.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Jun 2012 19:19:56 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/option-interface-blocked-mgmt-data-traffic/m-p/63956#M5803</guid>
      <dc:creator>Andre_Clark</dc:creator>
      <dc:date>2012-06-15T19:19:56Z</dc:date>
    </item>
    <item>
      <title>Re: option interface.blocked.mgmt_data_traffic</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/option-interface-blocked-mgmt-data-traffic/m-p/63961#M5804</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just found this... in the ifconfig the "no_ddns" parameter...&amp;nbsp;&amp;nbsp; &lt;STRONG&gt;ifconfig e0M no_ddns IP_address&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Jun 2012 19:53:56 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/option-interface-blocked-mgmt-data-traffic/m-p/63961#M5804</guid>
      <dc:creator>scottgelb</dc:creator>
      <dc:date>2012-06-15T19:53:56Z</dc:date>
    </item>
  </channel>
</rss>

