<?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: Problem with VLAN and VIF in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Problem-with-VLAN-and-VIF/m-p/18891#M4451</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;On the switch port, Vlan 1 must be a Tagged interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With Data Ontap 7.x, when you create a Vlan on top of a Vif (or physical interface), all traffic must be tagged with a VLAN ID number.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So your configuration is correct from the Data Ontap side (vlan create TRUNK-A 1 100), you just have to tag the port for Vlan 1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With Data Ontap 8.0.1 (I believe), you can have a Vlan tag on top of a VIF but still pass un-tagged packets.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can't do that with the current releases of Data Ontap.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you can't tag the port for VLAN 1, then you'll have to use a different VLAN tag number for the traffic on the 192.168.1.x subnet.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 04 Nov 2010 21:57:30 GMT</pubDate>
    <dc:creator>giuliano</dc:creator>
    <dc:date>2010-11-04T21:57:30Z</dc:date>
    <item>
      <title>Problem with VLAN and VIF</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Problem-with-VLAN-and-VIF/m-p/18887#M4449</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I try to enable vlan on my virtual interface, but i have a problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I use vlan 1, for my lan-data, and vlan 100 for iscsi.&lt;/P&gt;&lt;P&gt;In my switch, the port is configured as :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;vlan 1 untagged&lt;/P&gt;&lt;P&gt;vlan 100 tagged&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;without create vlan on my vif, network working good !&lt;/P&gt;&lt;P&gt;but when i try to enable vlan on my vif, network doesn't work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;to create vlan on my vif, i use CLI :&lt;/P&gt;&lt;P&gt;My vif is named TRUNK-A&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;vlan create TRUNK-A 1 100&lt;/P&gt;&lt;P&gt;ifconfig TRUNK-A-1 192.168.1.15 netmask 255.255.255.0&lt;/P&gt;&lt;P&gt;ifconfig TRUNK-A-100 192.168.100.15 netmask 255.255.255.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;so when i do this, interface 192.168.100.15 is up and responding, but interface in 192.168.1.15 not responding.&lt;/P&gt;&lt;P&gt;I use Procurve 2910-al switch.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any have an idea ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 07:06:08 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Problem-with-VLAN-and-VIF/m-p/18887#M4449</guid>
      <dc:creator>ademuynck</dc:creator>
      <dc:date>2025-06-05T07:06:08Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with VLAN and VIF</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Problem-with-VLAN-and-VIF/m-p/18891#M4451</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;On the switch port, Vlan 1 must be a Tagged interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With Data Ontap 7.x, when you create a Vlan on top of a Vif (or physical interface), all traffic must be tagged with a VLAN ID number.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So your configuration is correct from the Data Ontap side (vlan create TRUNK-A 1 100), you just have to tag the port for Vlan 1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With Data Ontap 8.0.1 (I believe), you can have a Vlan tag on top of a VIF but still pass un-tagged packets.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can't do that with the current releases of Data Ontap.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you can't tag the port for VLAN 1, then you'll have to use a different VLAN tag number for the traffic on the 192.168.1.x subnet.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Nov 2010 21:57:30 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Problem-with-VLAN-and-VIF/m-p/18891#M4451</guid>
      <dc:creator>giuliano</dc:creator>
      <dc:date>2010-11-04T21:57:30Z</dc:date>
    </item>
  </channel>
</rss>

