<?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 mvif switch to other mvif unexpectedly in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/mvif-switch-to-other-mvif-unexpectedly/m-p/17231#M4048</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;IHAC setting up a second level VIF. One svif has 2 mvifs, each mvif has 3 physical interfaces. config as below:&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;vif create lacp mvif0 -b ip e0a e0b e4d&lt;/P&gt;&lt;P&gt;vif create lacp mvif1 -b ip e4a e4b e4c&lt;/P&gt;&lt;P&gt;vif create single svif0 mvif0 mvif1&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When we physically disconnect one interface from the active mvif, it switched to other mvif unexpectedly. e.g when e0a was disconnected, mvif0 switched to mvif1; when e4a was disconnected, mvif1 switched to mvif0. This should not be the case as this is mvif, it should only switch to other mvif when all the physical interfaces are dead or physically disconnected. The console message as beow:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;SPAN style="color: #ff00ff; font-size: 10pt; "&gt;Sat Nov 13 10:44:12 HKT [FASHK02A: netif.linkDown:info]: Ethernet e4a: Link down, check cable.&lt;/SPAN&gt;&lt;/PRE&gt;&lt;PRE&gt;&lt;SPAN style="color: #ff00ff; font-size: 10pt; "&gt;Sat Nov 13 10:44:13 HKT [FASHK02A: pvif.switchLink:warning]: svif0: switching to mvif0&lt;/SPAN&gt;&lt;/PRE&gt;&lt;PRE&gt;&lt;SPAN style="color: #ff00ff; font-size: 10pt; "&gt; &lt;/SPAN&gt;&lt;/PRE&gt;&lt;PRE&gt;&lt;SPAN style="color: #ff00ff; font-size: 10pt; "&gt;Sat Nov 13 10:44:34 HKT [FASHK02A: netif.linkUp:info]: Ethernet e4a: Link up.&lt;/SPAN&gt;&lt;/PRE&gt;&lt;PRE&gt;&lt;SPAN style="color: #ff00ff; font-size: 10pt; "&gt; &lt;/SPAN&gt;&lt;/PRE&gt;&lt;PRE&gt;&lt;SPAN style="color: #ff00ff; font-size: 10pt; "&gt;Sat Nov 13 10:45:16 HKT [FASHK02A: netif.linkDown:info]: Ethernet e0a: Link down, check cable.&lt;/SPAN&gt;&lt;/PRE&gt;&lt;PRE&gt;&lt;SPAN style="color: #ff00ff; font-size: 10pt; "&gt; &lt;/SPAN&gt;&lt;/PRE&gt;&lt;PRE&gt;&lt;SPAN style="color: #ff00ff; font-size: 10pt; "&gt;Sat Nov 13 10:45:17 HKT [FASHK02A: pvif.switchLink:warning]: svif0: switching to mvif1&lt;/SPAN&gt;&lt;/PRE&gt;&lt;PRE&gt;&lt;SPAN style="color: #ff00ff; font-size: 10pt; "&gt; &lt;/SPAN&gt;&lt;/PRE&gt;&lt;PRE&gt;&lt;SPAN style="color: #ff00ff; font-size: 10pt; "&gt;Sat Nov 13 10:45:33 HKT [FASHK02A: netif.linkUp:info]: Ethernet e0a: Link up.&lt;/SPAN&gt;&lt;/PRE&gt;&lt;PRE&gt;&lt;BR /&gt;&lt;/PRE&gt;&lt;P&gt;Any idea?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #ff00ff;"&gt;The network switch side setting :&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;interface port-channel20&lt;BR /&gt;&amp;nbsp; description Etherchannel to fashk02a&lt;BR /&gt;&amp;nbsp; switchport access vlan 610&lt;BR /&gt;&amp;nbsp; spanning-tree guard root&lt;BR /&gt;&amp;nbsp; flowcontrol receive on&lt;BR /&gt; &lt;/P&gt;&lt;P&gt;interface port-channel21&lt;BR /&gt;&amp;nbsp; description Etherchannel to fashk02b&lt;BR /&gt;&amp;nbsp; switchport access vlan 610&lt;BR /&gt;&amp;nbsp; spanning-tree guard root&lt;BR /&gt;&amp;nbsp; flowcontrol receive on&lt;BR /&gt; &lt;/P&gt;&lt;P&gt;interface Ethernet150/1/11&lt;BR /&gt;&amp;nbsp; description fashk02a-e0a&lt;BR /&gt;&amp;nbsp; no cdp enable&lt;BR /&gt;&amp;nbsp; switchport access vlan 610&lt;BR /&gt;&amp;nbsp; spanning-tree guard root&lt;BR /&gt;&amp;nbsp; flowcontrol receive on&lt;BR /&gt;&amp;nbsp; no snmp trap link-status&lt;BR /&gt;&amp;nbsp; channel-group 20 mode active&lt;BR /&gt; &lt;BR /&gt;interface Ethernet150/1/12&lt;BR /&gt;&amp;nbsp; description fashk02a-e0b&lt;BR /&gt;&amp;nbsp; no cdp enable&lt;BR /&gt;&amp;nbsp; switchport access vlan 610&lt;BR /&gt;&amp;nbsp; spanning-tree guard root&lt;BR /&gt;&amp;nbsp; flowcontrol receive on&lt;BR /&gt;&amp;nbsp; no snmp trap link-status&lt;BR /&gt;&amp;nbsp; channel-group 20 mode active&lt;BR /&gt; &lt;BR /&gt;interface Ethernet150/1/13&lt;BR /&gt;&amp;nbsp; description fashk02a-e4d&lt;BR /&gt;&amp;nbsp; no cdp enable&lt;BR /&gt;&amp;nbsp; switchport access vlan 610&lt;BR /&gt;&amp;nbsp; spanning-tree guard root&lt;BR /&gt;&amp;nbsp; flowcontrol receive on&lt;BR /&gt;&amp;nbsp; no snmp trap link-status&lt;BR /&gt;&amp;nbsp; channel-group 20 mode active&lt;BR /&gt; &lt;BR /&gt;interface Ethernet150/1/14&lt;BR /&gt;&amp;nbsp; description fashk02b-e0a&lt;BR /&gt;&amp;nbsp; no cdp enable&lt;BR /&gt;&amp;nbsp; switchport access vlan 610&lt;BR /&gt;&amp;nbsp; spanning-tree guard root&lt;BR /&gt;&amp;nbsp; flowcontrol receive on&lt;BR /&gt;&amp;nbsp; no snmp trap link-status&lt;BR /&gt;&amp;nbsp; channel-group 21 mode active&lt;BR /&gt; &lt;BR /&gt;interface Ethernet150/1/15&lt;BR /&gt;&amp;nbsp; description fashk02b-e0b&lt;BR /&gt;&amp;nbsp; no cdp enable&lt;BR /&gt;&amp;nbsp; switchport access vlan 610&lt;BR /&gt;&amp;nbsp; spanning-tree guard root&lt;BR /&gt;&amp;nbsp; flowcontrol receive on&lt;BR /&gt;&amp;nbsp; no snmp trap link-status&lt;BR /&gt;&amp;nbsp; channel-group 21 mode active&lt;BR /&gt; &lt;BR /&gt;interface Ethernet150/1/16&lt;BR /&gt;&amp;nbsp; description fashk02b-e4d&lt;BR /&gt;&amp;nbsp; no cdp enable&lt;BR /&gt;&amp;nbsp; switchport access vlan 610&lt;BR /&gt;&amp;nbsp; spanning-tree guard root&lt;BR /&gt;&amp;nbsp; flowcontrol receive on&lt;BR /&gt;&amp;nbsp; no snmp trap link-status&lt;BR /&gt;&amp;nbsp; channel-group 21 mode active&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Terrence &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Jun 2025 07:05:22 GMT</pubDate>
    <dc:creator>tatlee</dc:creator>
    <dc:date>2025-06-05T07:05:22Z</dc:date>
    <item>
      <title>mvif switch to other mvif unexpectedly</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/mvif-switch-to-other-mvif-unexpectedly/m-p/17231#M4048</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;IHAC setting up a second level VIF. One svif has 2 mvifs, each mvif has 3 physical interfaces. config as below:&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;vif create lacp mvif0 -b ip e0a e0b e4d&lt;/P&gt;&lt;P&gt;vif create lacp mvif1 -b ip e4a e4b e4c&lt;/P&gt;&lt;P&gt;vif create single svif0 mvif0 mvif1&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When we physically disconnect one interface from the active mvif, it switched to other mvif unexpectedly. e.g when e0a was disconnected, mvif0 switched to mvif1; when e4a was disconnected, mvif1 switched to mvif0. This should not be the case as this is mvif, it should only switch to other mvif when all the physical interfaces are dead or physically disconnected. The console message as beow:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;SPAN style="color: #ff00ff; font-size: 10pt; "&gt;Sat Nov 13 10:44:12 HKT [FASHK02A: netif.linkDown:info]: Ethernet e4a: Link down, check cable.&lt;/SPAN&gt;&lt;/PRE&gt;&lt;PRE&gt;&lt;SPAN style="color: #ff00ff; font-size: 10pt; "&gt;Sat Nov 13 10:44:13 HKT [FASHK02A: pvif.switchLink:warning]: svif0: switching to mvif0&lt;/SPAN&gt;&lt;/PRE&gt;&lt;PRE&gt;&lt;SPAN style="color: #ff00ff; font-size: 10pt; "&gt; &lt;/SPAN&gt;&lt;/PRE&gt;&lt;PRE&gt;&lt;SPAN style="color: #ff00ff; font-size: 10pt; "&gt;Sat Nov 13 10:44:34 HKT [FASHK02A: netif.linkUp:info]: Ethernet e4a: Link up.&lt;/SPAN&gt;&lt;/PRE&gt;&lt;PRE&gt;&lt;SPAN style="color: #ff00ff; font-size: 10pt; "&gt; &lt;/SPAN&gt;&lt;/PRE&gt;&lt;PRE&gt;&lt;SPAN style="color: #ff00ff; font-size: 10pt; "&gt;Sat Nov 13 10:45:16 HKT [FASHK02A: netif.linkDown:info]: Ethernet e0a: Link down, check cable.&lt;/SPAN&gt;&lt;/PRE&gt;&lt;PRE&gt;&lt;SPAN style="color: #ff00ff; font-size: 10pt; "&gt; &lt;/SPAN&gt;&lt;/PRE&gt;&lt;PRE&gt;&lt;SPAN style="color: #ff00ff; font-size: 10pt; "&gt;Sat Nov 13 10:45:17 HKT [FASHK02A: pvif.switchLink:warning]: svif0: switching to mvif1&lt;/SPAN&gt;&lt;/PRE&gt;&lt;PRE&gt;&lt;SPAN style="color: #ff00ff; font-size: 10pt; "&gt; &lt;/SPAN&gt;&lt;/PRE&gt;&lt;PRE&gt;&lt;SPAN style="color: #ff00ff; font-size: 10pt; "&gt;Sat Nov 13 10:45:33 HKT [FASHK02A: netif.linkUp:info]: Ethernet e0a: Link up.&lt;/SPAN&gt;&lt;/PRE&gt;&lt;PRE&gt;&lt;BR /&gt;&lt;/PRE&gt;&lt;P&gt;Any idea?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #ff00ff;"&gt;The network switch side setting :&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;interface port-channel20&lt;BR /&gt;&amp;nbsp; description Etherchannel to fashk02a&lt;BR /&gt;&amp;nbsp; switchport access vlan 610&lt;BR /&gt;&amp;nbsp; spanning-tree guard root&lt;BR /&gt;&amp;nbsp; flowcontrol receive on&lt;BR /&gt; &lt;/P&gt;&lt;P&gt;interface port-channel21&lt;BR /&gt;&amp;nbsp; description Etherchannel to fashk02b&lt;BR /&gt;&amp;nbsp; switchport access vlan 610&lt;BR /&gt;&amp;nbsp; spanning-tree guard root&lt;BR /&gt;&amp;nbsp; flowcontrol receive on&lt;BR /&gt; &lt;/P&gt;&lt;P&gt;interface Ethernet150/1/11&lt;BR /&gt;&amp;nbsp; description fashk02a-e0a&lt;BR /&gt;&amp;nbsp; no cdp enable&lt;BR /&gt;&amp;nbsp; switchport access vlan 610&lt;BR /&gt;&amp;nbsp; spanning-tree guard root&lt;BR /&gt;&amp;nbsp; flowcontrol receive on&lt;BR /&gt;&amp;nbsp; no snmp trap link-status&lt;BR /&gt;&amp;nbsp; channel-group 20 mode active&lt;BR /&gt; &lt;BR /&gt;interface Ethernet150/1/12&lt;BR /&gt;&amp;nbsp; description fashk02a-e0b&lt;BR /&gt;&amp;nbsp; no cdp enable&lt;BR /&gt;&amp;nbsp; switchport access vlan 610&lt;BR /&gt;&amp;nbsp; spanning-tree guard root&lt;BR /&gt;&amp;nbsp; flowcontrol receive on&lt;BR /&gt;&amp;nbsp; no snmp trap link-status&lt;BR /&gt;&amp;nbsp; channel-group 20 mode active&lt;BR /&gt; &lt;BR /&gt;interface Ethernet150/1/13&lt;BR /&gt;&amp;nbsp; description fashk02a-e4d&lt;BR /&gt;&amp;nbsp; no cdp enable&lt;BR /&gt;&amp;nbsp; switchport access vlan 610&lt;BR /&gt;&amp;nbsp; spanning-tree guard root&lt;BR /&gt;&amp;nbsp; flowcontrol receive on&lt;BR /&gt;&amp;nbsp; no snmp trap link-status&lt;BR /&gt;&amp;nbsp; channel-group 20 mode active&lt;BR /&gt; &lt;BR /&gt;interface Ethernet150/1/14&lt;BR /&gt;&amp;nbsp; description fashk02b-e0a&lt;BR /&gt;&amp;nbsp; no cdp enable&lt;BR /&gt;&amp;nbsp; switchport access vlan 610&lt;BR /&gt;&amp;nbsp; spanning-tree guard root&lt;BR /&gt;&amp;nbsp; flowcontrol receive on&lt;BR /&gt;&amp;nbsp; no snmp trap link-status&lt;BR /&gt;&amp;nbsp; channel-group 21 mode active&lt;BR /&gt; &lt;BR /&gt;interface Ethernet150/1/15&lt;BR /&gt;&amp;nbsp; description fashk02b-e0b&lt;BR /&gt;&amp;nbsp; no cdp enable&lt;BR /&gt;&amp;nbsp; switchport access vlan 610&lt;BR /&gt;&amp;nbsp; spanning-tree guard root&lt;BR /&gt;&amp;nbsp; flowcontrol receive on&lt;BR /&gt;&amp;nbsp; no snmp trap link-status&lt;BR /&gt;&amp;nbsp; channel-group 21 mode active&lt;BR /&gt; &lt;BR /&gt;interface Ethernet150/1/16&lt;BR /&gt;&amp;nbsp; description fashk02b-e4d&lt;BR /&gt;&amp;nbsp; no cdp enable&lt;BR /&gt;&amp;nbsp; switchport access vlan 610&lt;BR /&gt;&amp;nbsp; spanning-tree guard root&lt;BR /&gt;&amp;nbsp; flowcontrol receive on&lt;BR /&gt;&amp;nbsp; no snmp trap link-status&lt;BR /&gt;&amp;nbsp; channel-group 21 mode active&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Terrence &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 07:05:22 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/mvif-switch-to-other-mvif-unexpectedly/m-p/17231#M4048</guid>
      <dc:creator>tatlee</dc:creator>
      <dc:date>2025-06-05T07:05:22Z</dc:date>
    </item>
    <item>
      <title>Re: mvif switch to other mvif unexpectedly</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/mvif-switch-to-other-mvif-unexpectedly/m-p/17235#M4049</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Terrence,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;you could give the "vif favor" command a try:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;vif create lacp mvif0 -b ip e0a e0b e4d&lt;/P&gt;&lt;P&gt;vif create lacp mvif1 -b ip e4a e4b e4c&lt;/P&gt;&lt;P&gt;vif create single svif0 mvif0 mvif1&lt;/P&gt;&lt;P&gt;vif favor mvif0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So the single vif favors the mvif0.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If this wont help, my guess would be sort of hidden option, how is this option set on your filer?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;filer&amp;gt; priv set diag&lt;/P&gt;&lt;P&gt;filer*&amp;gt; registry walk options.vif&lt;BR /&gt;options.vif.failover.link_degraded=off&lt;/P&gt;&lt;P&gt;filer*&amp;gt; priv set&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Thomas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Nov 2010 07:59:48 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/mvif-switch-to-other-mvif-unexpectedly/m-p/17235#M4049</guid>
      <dc:creator>thomas_glodde</dc:creator>
      <dc:date>2010-11-16T07:59:48Z</dc:date>
    </item>
    <item>
      <title>Re: mvif switch to other mvif unexpectedly</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/mvif-switch-to-other-mvif-unexpectedly/m-p/17240#M4050</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Thomas,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your advise. However, the customer is not requiring a vif favor. So, I don't think this is an option. Also, this isn't solve the problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The "options.vif.failover.link_degraded' is set to off, so it should not failover to the higher bandwidth mvif.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Terrence&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Nov 2010 09:06:06 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/mvif-switch-to-other-mvif-unexpectedly/m-p/17240#M4050</guid>
      <dc:creator>tatlee</dc:creator>
      <dc:date>2010-11-16T09:06:06Z</dc:date>
    </item>
    <item>
      <title>Re: mvif switch to other mvif unexpectedly</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/mvif-switch-to-other-mvif-unexpectedly/m-p/17245#M4051</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;you should get in contact with NGS then and have the pros check that matter out.&lt;/P&gt;&lt;P&gt;Kind regards&lt;/P&gt;&lt;P&gt;Thomas &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Nov 2010 10:01:35 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/mvif-switch-to-other-mvif-unexpectedly/m-p/17245#M4051</guid>
      <dc:creator>thomas_glodde</dc:creator>
      <dc:date>2010-11-16T10:01:35Z</dc:date>
    </item>
    <item>
      <title>Re: mvif switch to other mvif unexpectedly</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/mvif-switch-to-other-mvif-unexpectedly/m-p/17250#M4052</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;today i realized that i have the same problem.&lt;/P&gt;&lt;P&gt;has there been a resolution to this issue?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i would be highly interested!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edit: found this in the Network Administration Guide, maybe it applied to your environment:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"If you create a second-level vif over two&lt;/P&gt;&lt;DIV id="_mcePaste"&gt;multimode vifs that are connected to two different switches, you should connect the two switches&lt;/DIV&gt;&lt;DIV id="_mcePaste"&gt;with an inter-switch link (ISL)."&lt;/DIV&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV&gt;So i guess we cant go without an ISL. &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Feb 2011 19:28:55 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/mvif-switch-to-other-mvif-unexpectedly/m-p/17250#M4052</guid>
      <dc:creator>alexander_duske</dc:creator>
      <dc:date>2011-02-04T19:28:55Z</dc:date>
    </item>
    <item>
      <title>Re: mvif switch to other mvif unexpectedly</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/mvif-switch-to-other-mvif-unexpectedly/m-p/17255#M4053</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;we have now implemented an ISL between the two switches and everything works fine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;in question is the exact sense of having a redundant link, that switches when only one&amp;nbsp; link is down.&lt;/P&gt;&lt;P&gt;maybe this is just for load-balancing purposes??&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Mar 2011 09:11:50 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/mvif-switch-to-other-mvif-unexpectedly/m-p/17255#M4053</guid>
      <dc:creator>alexander_duske</dc:creator>
      <dc:date>2011-03-17T09:11:50Z</dc:date>
    </item>
  </channel>
</rss>

