<?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: multi/lacp vif that allows multiple vlans in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/multi-lacp-vif-that-allows-multiple-vlans/m-p/21228#M19129</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Seth,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes I did eventually figure it out and forgot to post it on here.&amp;nbsp; I know that using vlan 1 isn't a good idea but can't get the client to change it, as of right now. So to get around it I did e0a and e0b in one vif (not tagged) and e0c and eod in another (tagged for the vlan), isn't ideal but a start.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the reply though.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jake S&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 31 Jan 2012 19:08:31 GMT</pubDate>
    <dc:creator>jake_struve</dc:creator>
    <dc:date>2012-01-31T19:08:31Z</dc:date>
    <item>
      <title>multi/lacp vif that allows multiple vlans</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/multi-lacp-vif-that-allows-multiple-vlans/m-p/21216#M19127</link>
      <description>&lt;P&gt;Hello everyone,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am trying to setup a vif that will allow my production network and my nfs network to work across the vif.&amp;nbsp; Currently it is working with the vlan 172(NFS) but not the vlan 1(production).&amp;nbsp; I am going to attach some configs to see if anyone can help and tell me where im messed up at.&amp;nbsp; I have verified the cisco side and the netapp side but for some reason only half of this is working.&amp;nbsp; One more thing i have tried is just to assign the vlan1 to the vif before adding the vlan172.&amp;nbsp; When i do this it wont talk at all.&amp;nbsp; I am kind of leaning towards something on my cisco switch but i need some more eyes to help out.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Struv&lt;/P&gt;</description>
      <pubDate>Thu, 05 Jun 2025 07:10:22 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/multi-lacp-vif-that-allows-multiple-vlans/m-p/21216#M19127</guid>
      <dc:creator>jake_struve</dc:creator>
      <dc:date>2025-06-05T07:10:22Z</dc:date>
    </item>
    <item>
      <title>Re: multi/lacp vif that allows multiple vlans</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/multi-lacp-vif-that-allows-multiple-vlans/m-p/21220#M19128</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So, I'm sure you've long since figured this out, but for posterity: the native VLAN on Cisco switches is 1, and by default tags for the native VLAN &lt;STRONG&gt;are not sent&lt;/STRONG&gt;across trunks.&amp;nbsp; In general, I'd recommend that you move your production data network onto a different VLAN.﻿&amp;nbsp; Easier said than done, I know, but running data on the native VLAN is not recommended (for a number of reasons, some of which you've experienced).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH,&lt;/P&gt;&lt;P&gt;Seth&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 31 Jan 2012 19:01:11 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/multi-lacp-vif-that-allows-multiple-vlans/m-p/21220#M19128</guid>
      <dc:creator>sethm</dc:creator>
      <dc:date>2012-01-31T19:01:11Z</dc:date>
    </item>
    <item>
      <title>Re: multi/lacp vif that allows multiple vlans</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/multi-lacp-vif-that-allows-multiple-vlans/m-p/21228#M19129</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Seth,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes I did eventually figure it out and forgot to post it on here.&amp;nbsp; I know that using vlan 1 isn't a good idea but can't get the client to change it, as of right now. So to get around it I did e0a and e0b in one vif (not tagged) and e0c and eod in another (tagged for the vlan), isn't ideal but a start.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the reply though.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jake S&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 31 Jan 2012 19:08:31 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/multi-lacp-vif-that-allows-multiple-vlans/m-p/21228#M19129</guid>
      <dc:creator>jake_struve</dc:creator>
      <dc:date>2012-01-31T19:08:31Z</dc:date>
    </item>
  </channel>
</rss>

