<?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: Need to change the ifgrp distribution function from IP to port  for cluster in Production in ONTAP Hardware</title>
    <link>https://community.netapp.com/t5/ONTAP-Hardware/Need-to-change-the-ifgrp-distribution-function-from-IP-to-port-for-cluster-in/m-p/134942#M8441</link>
    <description>&lt;P&gt;Hello, as I think you've already realised to change the distribution function is disruptive in that you must delete the interface group.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, it&amp;nbsp;should be&amp;nbsp;possible to achieve this,&amp;nbsp;albeit a manual LIF failover will incur a&amp;nbsp;15 second disruption:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;First remove a port from the ifgrp - &lt;STRONG&gt;network port ifgrp remove-port&lt;/STRONG&gt;&lt;/LI&gt;&lt;LI&gt;Create a new ifgrp with the "port" &lt;SPAN&gt;distribution function&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;Migrate the LIF from the old to the new ifgrp -&amp;nbsp;&amp;nbsp;&lt;STRONG&gt;network interface migrate &lt;/STRONG&gt;(&lt;U&gt;15 second disruption&lt;/U&gt;)&lt;/LI&gt;&lt;LI&gt;Delete the old ifgrp and add the second port to the new ifgrp -&amp;nbsp;&lt;STRONG&gt;network port ifgrp add-port&lt;/STRONG&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Just a&amp;nbsp;caution from&amp;nbsp;Ethernet Storage Design Considerations and Best Practices for Clustered Data ONTAP Configurations - &lt;A href="http://www.netapp.com/us/media/tr-4182.pdf" target="_blank"&gt;http://www.netapp.com/us/media/tr-4182.pdf&lt;/A&gt; page 13:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;Port&lt;/STRONG&gt;. Use this distribution method for optimal load-balancing results. However, it doesn’t lend itself as well to troubleshooting, because the TCP/UDP port of a packet is also used to determine the physical port that is used to send a particular packet. It has also been reported that switches operating in particular modes (mapping MAC/IP/port) might exhibit lower than expected performance in this mode.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;...If you use “port” on the IFGRP configuration on the cluster, make sure that the switch port on the Cisco, Juniper, Brocade, or other device is also configured in the same way&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Obviously this is Production so test in your environment first, however hope you find this useful.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Grant.&lt;/P&gt;</description>
    <pubDate>Tue, 03 Oct 2017 13:40:54 GMT</pubDate>
    <dc:creator>sgrant</dc:creator>
    <dc:date>2017-10-03T13:40:54Z</dc:date>
    <item>
      <title>Need to change the ifgrp distribution function from IP to port  for cluster in Production</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Need-to-change-the-ifgrp-distribution-function-from-IP-to-port-for-cluster-in/m-p/134936#M8440</link>
      <description>&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Port&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Distribution&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Active&lt;BR /&gt;Node&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; IfGrp&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Function&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; MAC Address&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Ports&amp;nbsp;&amp;nbsp; Ports&lt;BR /&gt;-------- ---------- ------------ ----------------- ------- -------------------&lt;BR /&gt;netappind001-n1&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; a1a&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ip&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ################### full&amp;nbsp;&amp;nbsp;&amp;nbsp; e0c, e0d&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; a1c&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ip&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ################### full&amp;nbsp;&amp;nbsp;&amp;nbsp; e0e, e0f&lt;BR /&gt;netappind001-n2&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; a2a&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ip&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ################### full&amp;nbsp;&amp;nbsp;&amp;nbsp; e0c, e0d&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; a2c&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ip&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ################### full&amp;nbsp;&amp;nbsp;&amp;nbsp; e0e, e0f&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have seleceted 'Distribution Function' as 'IP' for our two port ifgrp and now observing issue with outgoing traffic -&amp;nbsp; one of the port in ifgrp is heavily utilised while the other is less utilised&amp;nbsp; (difference is huge)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Since we have all 1 GB ports so need to utilise both the ports in order to get fair outgoing bandwidth.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Now the problem is that this cluster is in production - is there anyway we can change the Distribution Function to port without / min downtime.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Attached logs below to show that e0d port in ifgrp a1a is more utilised than e0c&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;-- interface&amp;nbsp; a1a-4&amp;nbsp; (12 days, 20 hours, 18 minutes, 10 seconds) --&lt;BR /&gt;&lt;BR /&gt;RECEIVE&lt;BR /&gt;&amp;nbsp;Total frames:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 310m | Total bytes:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 22370m | Multi/broadcast:&amp;nbsp; 2553k&lt;BR /&gt;TRANSMIT&lt;BR /&gt;&amp;nbsp;Total frames:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2027m | Total bytes:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 3049g | Multi/broadcast:&amp;nbsp;&amp;nbsp; 161&lt;BR /&gt;&amp;nbsp;Queue overflows:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&lt;BR /&gt;LINK INFO&lt;BR /&gt;&amp;nbsp;Linkup Events:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2&amp;nbsp; | Allocs Failed:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&lt;BR /&gt;DEVICE&lt;BR /&gt;&amp;nbsp;Vlan ID:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 4&amp;nbsp; | Phy Iface:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; a1a&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;-- interface&amp;nbsp; e0c&amp;nbsp; (12 days, 20 hours, 18 minutes, 10 seconds) --&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;TRANSMIT&lt;BR /&gt;&amp;nbsp;Frames/second:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 4&amp;nbsp; | Bytes/second:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 632&amp;nbsp; | Errors/minute:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&lt;BR /&gt;&amp;nbsp;Discards/minute:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp; | Total frames:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 5855k | Total bytes:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 61442m&lt;BR /&gt;&amp;nbsp;Total errors:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp; | Total discards:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp; | Multi/broadcast: 16692&lt;BR /&gt;&amp;nbsp;Queue overflows:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp; | No buffers:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp; | Transmit error:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&lt;BR /&gt;&amp;nbsp;Frame Dropped:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp; | Pause frame:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp; | Stray Cluster Pk:&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;-- interface&amp;nbsp; e0d&amp;nbsp; (12 days, 20 hours, 18 minutes, 10 seconds) --&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;TRANSMIT&lt;BR /&gt;&amp;nbsp;Frames/second:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 22&amp;nbsp; | Bytes/second:&amp;nbsp;&amp;nbsp;&amp;nbsp; 68014&amp;nbsp; | Errors/minute:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&lt;BR /&gt;&amp;nbsp;Discards/minute:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp; | Total frames:&amp;nbsp;&amp;nbsp;&amp;nbsp; 84223k | Total bytes:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1136g&lt;BR /&gt;&amp;nbsp;Total errors:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp; | Total discards:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp; | Multi/broadcast: 56431&lt;BR /&gt;&amp;nbsp;Queue overflows:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp; | No buffers:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp; | Transmit error:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&lt;BR /&gt;&amp;nbsp;Frame Dropped:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp; | Pause frame:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp; | Stray Cluster Pk:&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 14:31:51 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Need-to-change-the-ifgrp-distribution-function-from-IP-to-port-for-cluster-in/m-p/134936#M8440</guid>
      <dc:creator>Prawa</dc:creator>
      <dc:date>2025-06-04T14:31:51Z</dc:date>
    </item>
    <item>
      <title>Re: Need to change the ifgrp distribution function from IP to port  for cluster in Production</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Need-to-change-the-ifgrp-distribution-function-from-IP-to-port-for-cluster-in/m-p/134942#M8441</link>
      <description>&lt;P&gt;Hello, as I think you've already realised to change the distribution function is disruptive in that you must delete the interface group.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, it&amp;nbsp;should be&amp;nbsp;possible to achieve this,&amp;nbsp;albeit a manual LIF failover will incur a&amp;nbsp;15 second disruption:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;First remove a port from the ifgrp - &lt;STRONG&gt;network port ifgrp remove-port&lt;/STRONG&gt;&lt;/LI&gt;&lt;LI&gt;Create a new ifgrp with the "port" &lt;SPAN&gt;distribution function&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;Migrate the LIF from the old to the new ifgrp -&amp;nbsp;&amp;nbsp;&lt;STRONG&gt;network interface migrate &lt;/STRONG&gt;(&lt;U&gt;15 second disruption&lt;/U&gt;)&lt;/LI&gt;&lt;LI&gt;Delete the old ifgrp and add the second port to the new ifgrp -&amp;nbsp;&lt;STRONG&gt;network port ifgrp add-port&lt;/STRONG&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Just a&amp;nbsp;caution from&amp;nbsp;Ethernet Storage Design Considerations and Best Practices for Clustered Data ONTAP Configurations - &lt;A href="http://www.netapp.com/us/media/tr-4182.pdf" target="_blank"&gt;http://www.netapp.com/us/media/tr-4182.pdf&lt;/A&gt; page 13:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;Port&lt;/STRONG&gt;. Use this distribution method for optimal load-balancing results. However, it doesn’t lend itself as well to troubleshooting, because the TCP/UDP port of a packet is also used to determine the physical port that is used to send a particular packet. It has also been reported that switches operating in particular modes (mapping MAC/IP/port) might exhibit lower than expected performance in this mode.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;...If you use “port” on the IFGRP configuration on the cluster, make sure that the switch port on the Cisco, Juniper, Brocade, or other device is also configured in the same way&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Obviously this is Production so test in your environment first, however hope you find this useful.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Grant.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Oct 2017 13:40:54 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Need-to-change-the-ifgrp-distribution-function-from-IP-to-port-for-cluster-in/m-p/134942#M8441</guid>
      <dc:creator>sgrant</dc:creator>
      <dc:date>2017-10-03T13:40:54Z</dc:date>
    </item>
  </channel>
</rss>

