topic Re: vif has nfo enabled, can't add new vlan in ONTAP Discussions

topic Re: vif has nfo enabled, can't add new vlan in ONTAP Discussions https://community.netapp.com/t5/ONTAP-Discussions/vif-has-nfo-enabled-can-t-add-new-vlan/m-p/41512#M9768 <HTML><HEAD></HEAD><BODY><P>Hi All,</P><P></P><P><SPAN style="color: #1f497d;">I did some testing today, and unfortunately  it did not go too well, I was able to disable negotiated failover on my vif, </SPAN></P><P><SPAN style="color: #1f497d;">And then create the new vlans, but not re-enable it !</SPAN></P><P><SPAN style="color: #1f497d;"> </SPAN><SPAN style="color: #1f497d;"> </SPAN></P><P>WENETAPP2> vlan create vif1 20</P><P>vlan: Create failed. Negotiated failover is enabled on interface vif1.</P><P>WENETAPP2> ifconfig vif1 -nfo</P><P>WENETAPP2> Wed Nov 30 15:53:12 GMT [WENETAPP2: nbt.nbns.registrationComplete:info]: NBT: All CIFS name registrations have completed for the local server.</P><P>WENETAPP2> vlan create vif1 20</P><P>vlan: vif1-20 has been created</P><P>WENETAPP2> ifconfig vif1-20 192.168.1.33</P><P>WENETAPP2> ifconfig -a</P><P>e0M: flags=0x2108866<BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500</P><P>        ether 00:a0:98:29:45:4a (auto-unknown-cfg_down) flowcontrol full</P><P>e0a: flags=0x8ad08867<BROADCAST,RUNNING,MULTICAST,TCPCKSUM,VLAN> mtu 1500</P><P>        ether 02:a0:98:29:45:4a (auto-1000t-fd-up) flowcontrol full</P><P>        trunked vif1</P><P>e0b: flags=0x8ad08867<BROADCAST,RUNNING,MULTICAST,TCPCKSUM,VLAN> mtu 1500</P><P>        ether 02:a0:98:29:45:4a (auto-1000t-fd-up) flowcontrol full</P><P>        trunked vif1</P><P>lo: flags=0x1948049<UP,LOOPBACK,RUNNING,MULTICAST,TCPCKSUM> mtu 8160</P><P>        inet 127.0.0.1 netmask-or-prefix 0xff000000 broadcast 127.0.0.1</P><P>        ether 00:00:00:00:00:00 (VIA Provider)</P><P>vif1: flags=0xa2d08863<BROADCAST,RUNNING,MULTICAST,TCPCKSUM,VLAN> mtu 1500</P><P>        ether 02:a0:98:29:45:4a (Enabled virtual interface)</P><P>vif1-20: flags=0x2948863<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500</P><P>        inet 192.168.1.33 netmask-or-prefix 0xffffff00 broadcast 192.168.1.255</P><P>        ether 02:a0:98:29:45:4a (Enabled virtual interface)</P><P>WENETAPP2> vlan add vif1 30</P><P>vlan: vif1-30 has been created</P><P>WENETAPP2></P><P>WENETAPP2> ifconfig vif1-30 192.168.1.47</P><P>WENETAPP2> ifconfig -a</P><P>e0M: flags=0x2108866<BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500</P><P>        ether 00:a0:98:29:45:4a (auto-unknown-cfg_down) flowcontrol full</P><P>e0a: flags=0x8ad08867<BROADCAST,RUNNING,MULTICAST,TCPCKSUM,VLAN> mtu 1500</P><P>        ether 02:a0:98:29:45:4a (auto-1000t-fd-up) flowcontrol full</P><P>        trunked vif1</P><P>e0b: flags=0x8ad08867<BROADCAST,RUNNING,MULTICAST,TCPCKSUM,VLAN> mtu 1500</P><P>        ether 02:a0:98:29:45:4a (auto-1000t-fd-up) flowcontrol full</P><P>        trunked vif1</P><P>lo: flags=0x1948049<UP,LOOPBACK,RUNNING,MULTICAST,TCPCKSUM> mtu 8160</P><P>        inet 127.0.0.1 netmask-or-prefix 0xff000000 broadcast 127.0.0.1</P><P>        ether 00:00:00:00:00:00 (VIA Provider)</P><P>vif1: flags=0xa2d08863<BROADCAST,RUNNING,MULTICAST,TCPCKSUM,VLAN> mtu 1500</P><P>        ether 02:a0:98:29:45:4a (Enabled virtual interface)</P><P>vif1-20: flags=0x2948863<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500</P><P>        inet 192.168.1.33 netmask-or-prefix 0xffffff00 broadcast 192.168.1.255</P><P>        ether 02:a0:98:29:45:4a (Enabled virtual interface)</P><P>vif1-30: flags=0x2948863<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500</P><P>        inet 192.168.1.47 netmask-or-prefix 0xffffff00 broadcast 192.168.1.255</P><P>        ether 02:a0:98:29:45:4a (Enabled virtual interface)</P><P>WENETAPP2> ifconfig vif1 nfo</P><P>ifconfig: invalid option 'nfo' on a physical VLAN interface</P><P>usage: "ifconfig ?" will list the accepted subcommands and arguments</P><P>WENETAPP2></P><P></P><P>Any ideas ?</P><P></P><P>thanks and regards </P><P></P><P>Jack </P></BODY></HTML> Wed, 30 Nov 2011 17:03:21 GMT jack_quinn 2011-11-30T17:03:21Z vif has nfo enabled, can't add new vlan https://community.netapp.com/t5/ONTAP-Discussions/vif-has-nfo-enabled-can-t-add-new-vlan/m-p/41486#M9762 <HTML><HEAD></HEAD><BODY><P>Hi,</P><P></P><P>One of our customers has enabled network failover on 2nd level vifs for their cluster,</P><P>When trying to add a new vlan, they are getting error below</P><P></P><P>nbg2-fas13> vlan add fas13-2ndLvl01 316</P><P>vlan: Create failed. Negotiated failover is enabled on interface fas13-2ndLvl01.</P><P></P><P><SPAN style="color: #3366ff;">nbg2-fas13> ifconfig -a</SPAN></P><P><SPAN style="color: #3366ff;">e0a: flags=0x8af0c867<BROADCAST,RUNNING,MULTICAST,TCPCKSUM,VLAN> mtu 1500</SPAN></P><P><SPAN style="color: #3366ff;">        ether 02:1b:21:a8:22:e0 (auto-1000t-fd-up) flowcontrol full</SPAN></P><P><SPAN style="color: #3366ff;">        trunked cra03-1stLvl01</SPAN></P><P><SPAN style="color: #3366ff;">e0b: flags=0x8af0c867<BROADCAST,RUNNING,MULTICAST,TCPCKSUM,VLAN> mtu 1500</SPAN></P><P><SPAN style="color: #3366ff;">        ether 02:1b:21:a8:22:e0 (auto-1000t-fd-up) flowcontrol full</SPAN></P><P><SPAN style="color: #3366ff;">        trunked cra03-1stLvl01</SPAN></P><P><SPAN style="color: #3366ff;">e1a: flags=0x8af0c867<BROADCAST,RUNNING,MULTICAST,TCPCKSUM,VLAN> mtu 1500</SPAN></P><P><SPAN style="color: #3366ff;">        ether 02:1b:21:a8:22:e0 (auto-1000t-fd-up) flowcontrol full</SPAN></P><P><SPAN style="color: #3366ff;">        trunked cra04-1stLvl02</SPAN></P><P><SPAN style="color: #3366ff;">e1b: flags=0x8af0c867<BROADCAST,RUNNING,MULTICAST,TCPCKSUM,VLAN> mtu 1500</SPAN></P><P><SPAN style="color: #3366ff;">        ether 02:1b:21:a8:22:e0 (auto-1000t-fd-up) flowcontrol full</SPAN></P><P><SPAN style="color: #3366ff;">        trunked cra04-1stLvl02</SPAN></P><P><SPAN style="color: #3366ff;">e1c: flags=0x274c867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500</SPAN></P><P><SPAN style="color: #3366ff;">        inet 192.168.1.13 netmask 0xffffff00 broadcast 192.168.1.255</SPAN></P><P><SPAN style="color: #3366ff;">        ether 00:1b:21:a8:22:e2 (auto-unknown-down) flowcontrol full</SPAN></P><P><SPAN style="color: #3366ff;">e1d: flags=0x270c866<BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500</SPAN></P><P><SPAN style="color: #3366ff;">        ether 00:1b:21:a8:22:e3 (auto-unknown-down) flowcontrol full</SPAN></P><P><SPAN style="color: #3366ff;">c0a: flags=0x1f4c867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 9000 PRIVATE</SPAN></P><P><SPAN style="color: #3366ff;">        inet 192.168.1.183 netmask 0xffffff00 broadcast 192.168.1.255</SPAN></P><P><SPAN style="color: #3366ff;">        ether 00:a0:98:17:6c:ba (auto-10g_twinax-fd-up) flowcontrol full</SPAN></P><P><SPAN style="color: #3366ff;">c0b: flags=0x1f4c867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 9000 PRIVATE</SPAN></P><P><SPAN style="color: #3366ff;">        inet 192.168.2.79 netmask 0xffffff00 broadcast 192.168.2.255</SPAN></P><P><SPAN style="color: #3366ff;">        ether 00:a0:98:17:6c:bb (auto-10g_twinax-fd-up) flowcontrol full</SPAN></P><P><SPAN style="color: #3366ff;">e0M: flags=0x2b4c867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500</SPAN></P><P><SPAN style="color: #3366ff;">        inet 192.168.192.209 netmask 0xffffff00 broadcast 192.168.192.255</SPAN></P><P><SPAN style="color: #3366ff;">        partner e0M (not in use)</SPAN></P><P><SPAN style="color: #3366ff;">        ether 00:a0:98:17:6c:bc (auto-100tx-fd-up) flowcontrol full</SPAN></P><P><SPAN style="color: #3366ff;">e0P: flags=0x2b4c867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 PRIVATE</SPAN></P><P><SPAN style="color: #3366ff;">        inet 192.168.0.207 netmask 0xfffffc00 broadcast 192.168.3.255 noddns</SPAN></P><P><SPAN style="color: #3366ff;">        ether 00:a0:98:17:6c:bd (auto-100tx-fd-up) flowcontrol full</SPAN></P><P><SPAN style="color: #3366ff;">lo: flags=0x1b48049<UP,LOOPBACK,RUNNING,MULTICAST,TCPCKSUM> mtu 8160</SPAN></P><P><SPAN style="color: #3366ff;">        inet 127.0.0.1 netmask 0xff000000 broadcast 127.0.0.1</SPAN></P><P><SPAN style="color: #3366ff;">        ether 00:00:00:00:00:00 (RNIC Provider)</SPAN></P><P><SPAN style="color: #3366ff;">losk: flags=0x40a400c9<UP,LOOPBACK,RUNNING> mtu 9188</SPAN></P><P><SPAN style="color: #3366ff;">        inet 127.0.20.1 netmask 0xff000000 broadcast 127.0.20.1</SPAN></P><P><SPAN style="color: #3366ff;">cra03-1stLvl01: flags=0xaaf0c863<BROADCAST,RUNNING,MULTICAST,TCPCKSUM,VLAN> mtu 1500</SPAN></P><P><SPAN style="color: #3366ff;">        ether 02:1b:21:a8:22:e0 (Enabled interface groups)</SPAN></P><P><SPAN style="color: #3366ff;">        trunked fas13-2ndLvl01</SPAN></P><P><SPAN style="color: #3366ff;">cra04-1stLvl02: flags=0xaaf0c863<BROADCAST,RUNNING,MULTICAST,TCPCKSUM,VLAN> mtu 1500</SPAN></P><P><SPAN style="color: #3366ff;">        ether 02:1b:21:a8:22:e0 (Enabled interface groups)</SPAN></P><P><SPAN style="color: #3366ff;">        trunked fas13-2ndLvl01</SPAN></P><P><SPAN style="color: #3366ff;">fas13-2ndLvl01: flags=0xa2f0c863<BROADCAST,RUNNING,MULTICAST,TCPCKSUM,VLAN> mtu 1500</SPAN></P><P><SPAN style="color: #3366ff;">        partner fas14-2ndLvl01 (not in use)</SPAN></P><P><SPAN style="color: #3366ff;">        ether 02:1b:21:a8:22:e0 (Enabled interface groups)</SPAN></P><P><SPAN style="color: #3366ff;">        nfo enabled</SPAN></P><P><SPAN style="color: #3366ff;">fas13-2ndLv-301: flags=0x6b4c863<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM,NOWINS> mtu 1500</SPAN></P><P><SPAN style="color: #3366ff;">        inet 192.168.193.53 netmask 0xffffffc0 broadcast 192.168.193.63</SPAN></P><P><SPAN style="color: #3366ff;">        partner inet 192.168.193.54 (not in use)</SPAN></P><P><SPAN style="color: #3366ff;">        ether 02:1b:21:a8:22:e0 (Enabled interface groups)</SPAN></P><P><SPAN style="color: #3366ff;">fas13-2ndLv-631: flags=0x6b4c863<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM,NOWINS> mtu 1500</SPAN></P><P><SPAN style="color: #3366ff;">        inet 192.168.203.71 netmask 0xffffffc0 broadcast 192.168.203.127</SPAN></P><P><SPAN style="color: #3366ff;">        partner inet 192.168.203.72 (not in use)</SPAN></P><P><SPAN style="color: #3366ff;">        ether 02:1b:21:a8:22:e0 (Enabled interface groups)</SPAN></P><P><SPAN style="color: #3366ff;">fas13-2ndLv-601: flags=0x6b4c863<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM,NOWINS> mtu 1500</SPAN></P><P><SPAN style="color: #3366ff;">        inet 192.168.200.135 netmask 0xffffff80 broadcast 192.168.200.255</SPAN></P><P><SPAN style="color: #3366ff;">        partner inet 192.168.200.136 (not in use)</SPAN></P><P><SPAN style="color: #3366ff;">        ether 02:1b:21:a8:22:e0 (Enabled interface groups)</SPAN></P><P><SPAN style="color: #3366ff;">fas13-2ndLv-641: flags=0x6b4c863<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM,NOWINS> mtu 1500</SPAN></P><P><SPAN style="color: #3366ff;">        inet 192.168.204.135 netmask 0xffffff80 broadcast 192.168.204.255</SPAN></P><P><SPAN style="color: #3366ff;">        partner inet 192.168.204.136 (not in use)</SPAN></P><P><SPAN style="color: #3366ff;">        ether 02:1b:21:a8:22:e0 (Enabled interface groups)</SPAN></P><P><SPAN style="color: #3366ff;">fas13-2ndLv-650: flags=0x6b4c863<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM,NOWINS> mtu 1500</SPAN></P><P><SPAN style="color: #3366ff;">        inet 192.168.205.3 netmask 0xffffffe0 broadcast 192.168.205.31</SPAN></P><P><SPAN style="color: #3366ff;">        partner inet 192.168.205.4 (not in use)</SPAN></P><P><SPAN style="color: #3366ff;">        ether 02:1b:21:a8:22:e0 (Enabled interface groups)</SPAN></P><P><SPAN style="color: #3366ff;">nbg2-fas13></SPAN></P><P></P><P><SPAN style="color: #3366ff;">nbg2-fas13> rdfile /etc/rc</SPAN></P><P><SPAN style="color: #3366ff;">#Regenerated by registry Mon Nov 14 12:21:20 UTC 2011</SPAN></P><P><SPAN style="color: #3366ff;">#Auto-generated by setup Tue Sep 20 10:54:08 UTC 2011</SPAN></P><P><SPAN style="color: #3366ff;">hostname nbg2-fas13</SPAN></P><P><SPAN style="color: #3366ff;">ifgrp create multi cra03-1stLvl01 -b ip e0a e0b</SPAN></P><P><SPAN style="color: #3366ff;">ifgrp create multi cra04-1stLvl02 -b ip e1a e1b</SPAN></P><P><SPAN style="color: #3366ff;">ifgrp create single fas13-2ndLvl01 cra04-1stLvl02 cra03-1stLvl01</SPAN></P><P><SPAN style="color: #3366ff;">ifconfig fas13-2ndLv-301 192.168.193.53 netmask 255.255.255.192 mtusize 1500 -wins partner 192.168.193.54</SPAN></P><P><SPAN style="color: #3366ff;">ifconfig fas13-2ndLv-631 192.168.203.71 netmask 255.255.255.192 mtusize 1500 -wins partner 192.168.203.72</SPAN></P><P><SPAN style="color: #3366ff;">ifconfig fas13-2ndLv-601 192.168.200.135 netmask 255.255.255.128 mtusize 1500 -wins partner 192.168.200.136</SPAN></P><P><SPAN style="color: #3366ff;">ifconfig fas13-2ndLv-641 192.168.204.135 netmask 255.255.255.128 mtusize 1500 -wins partner 192.168.204.136</SPAN></P><P><SPAN style="color: #3366ff;">ifconfig fas13-2ndLv-650 192.168.205.3 netmask 255.255.255.224 mtusize 1500 -wins partner 192.168.205.4</SPAN></P><P><SPAN style="color: #3366ff;">ifconfig fas13-2ndLvl01 mediatype auto partner fas14-2ndLvl01</SPAN></P><P><SPAN style="color: #3366ff;">ifconfig e0M `hostname`-e0M flowcontrol full partner e0M</SPAN></P><P><SPAN style="color: #3366ff;">ifconfig e1c `hostname`-e1c mediatype auto flowcontrol full</SPAN></P><P><SPAN style="color: #3366ff;">ifconfig fas13-2ndLvl01 nfo</SPAN></P><P><SPAN style="color: #3366ff;">route add default 192.168.193.1 1</SPAN></P><P><SPAN style="color: #3366ff;">route add net 192.168.225/27 192.168.205.1 1</SPAN></P><P><SPAN style="color: #3366ff;">routed on</SPAN></P><P><SPAN style="color: #3366ff;">options dns.domainname lan.gasp2.newbay.com</SPAN></P><P><SPAN style="color: #3366ff;">options dns.enable on</SPAN></P><P><SPAN style="color: #3366ff;">options nis.enable off</SPAN></P><P><SPAN style="color: #3366ff;">savecore</SPAN></P><P></P><P></P><P>Do you think we could disable nfo, add new vlan, and then re-enable nfo ?</P><P></P><P>nbg2-fas13> ifconfig fas13-2ndLvl01 -nfo</P><P>nbg2-fas13> vlan add fas13-2ndLvl01 316</P><P><SPAN style="color: #000000;"><SPAN style="color: #808080;">nbg2-fas13></SPAN> </SPAN>ifconfig fas13-2ndLvl01 nfo</P><P></P><P></P><P>Thanks and regards</P><P></P><P>Jack </P></BODY></HTML> Thu, 05 Jun 2025 06:40:38 GMT https://community.netapp.com/t5/ONTAP-Discussions/vif-has-nfo-enabled-can-t-add-new-vlan/m-p/41486#M9762 jack_quinn 2025-06-05T06:40:38Z Re: vif has nfo enabled, can't add new vlan https://community.netapp.com/t5/ONTAP-Discussions/vif-has-nfo-enabled-can-t-add-new-vlan/m-p/41490#M9763 <HTML><HEAD></HEAD><BODY><P>That should work..you could also set nfo on each vlan ifconfig itself instead.</P></BODY></HTML> Fri, 25 Nov 2011 15:23:51 GMT https://community.netapp.com/t5/ONTAP-Discussions/vif-has-nfo-enabled-can-t-add-new-vlan/m-p/41490#M9763 scottgelb 2011-11-25T15:23:51Z Re: vif has nfo enabled, can't add new vlan https://community.netapp.com/t5/ONTAP-Discussions/vif-has-nfo-enabled-can-t-add-new-vlan/m-p/41498#M9765 <HTML><HEAD></HEAD><BODY><P>Thanks Scott, </P><P>We shall give that a go alright so</P><P></P><P>We would need to get an outage to test new /etc/rc config if we went to enable on each vlan config </P><P>and this particular customer won't allow changes to /etc/rc with change request and tests after changes made</P><P></P><P>regards</P><P></P><P>Jack </P></BODY></HTML> Fri, 25 Nov 2011 15:31:27 GMT https://community.netapp.com/t5/ONTAP-Discussions/vif-has-nfo-enabled-can-t-add-new-vlan/m-p/41498#M9765 jack_quinn 2011-11-25T15:31:27Z Re: vif has nfo enabled, can't add new vlan https://community.netapp.com/t5/ONTAP-Discussions/vif-has-nfo-enabled-can-t-add-new-vlan/m-p/41502#M9766 <HTML><HEAD></HEAD><BODY><DIV><P>Makes sense. I prefer customers that plan and schedule <span class="lia-unicode-emoji" title=":slightly_smiling_face:">🙂</span></P></DIV></BODY></HTML> Fri, 25 Nov 2011 16:04:34 GMT https://community.netapp.com/t5/ONTAP-Discussions/vif-has-nfo-enabled-can-t-add-new-vlan/m-p/41502#M9766 scottgelb 2011-11-25T16:04:34Z Re: vif has nfo enabled, can't add new vlan https://community.netapp.com/t5/ONTAP-Discussions/vif-has-nfo-enabled-can-t-add-new-vlan/m-p/41507#M9767 <HTML><HEAD></HEAD><BODY><P>Cheers Scott,</P><P></P><P>it's <A></A><A></A><A></A><A></A>the way we educate them <A></A><A></A><SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.netapp.com/5.0.1/images/emoticons/happy.gif"></SPAN> </P></BODY></HTML> Fri, 25 Nov 2011 16:22:56 GMT https://community.netapp.com/t5/ONTAP-Discussions/vif-has-nfo-enabled-can-t-add-new-vlan/m-p/41507#M9767 jack_quinn 2011-11-25T16:22:56Z Re: vif has nfo enabled, can't add new vlan https://community.netapp.com/t5/ONTAP-Discussions/vif-has-nfo-enabled-can-t-add-new-vlan/m-p/41512#M9768 <HTML><HEAD></HEAD><BODY><P>Hi All,</P><P></P><P><SPAN style="color: #1f497d;">I did some testing today, and unfortunately  it did not go too well, I was able to disable negotiated failover on my vif, </SPAN></P><P><SPAN style="color: #1f497d;">And then create the new vlans, but not re-enable it !</SPAN></P><P><SPAN style="color: #1f497d;"> </SPAN><SPAN style="color: #1f497d;"> </SPAN></P><P>WENETAPP2> vlan create vif1 20</P><P>vlan: Create failed. Negotiated failover is enabled on interface vif1.</P><P>WENETAPP2> ifconfig vif1 -nfo</P><P>WENETAPP2> Wed Nov 30 15:53:12 GMT [WENETAPP2: nbt.nbns.registrationComplete:info]: NBT: All CIFS name registrations have completed for the local server.</P><P>WENETAPP2> vlan create vif1 20</P><P>vlan: vif1-20 has been created</P><P>WENETAPP2> ifconfig vif1-20 192.168.1.33</P><P>WENETAPP2> ifconfig -a</P><P>e0M: flags=0x2108866<BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500</P><P>        ether 00:a0:98:29:45:4a (auto-unknown-cfg_down) flowcontrol full</P><P>e0a: flags=0x8ad08867<BROADCAST,RUNNING,MULTICAST,TCPCKSUM,VLAN> mtu 1500</P><P>        ether 02:a0:98:29:45:4a (auto-1000t-fd-up) flowcontrol full</P><P>        trunked vif1</P><P>e0b: flags=0x8ad08867<BROADCAST,RUNNING,MULTICAST,TCPCKSUM,VLAN> mtu 1500</P><P>        ether 02:a0:98:29:45:4a (auto-1000t-fd-up) flowcontrol full</P><P>        trunked vif1</P><P>lo: flags=0x1948049<UP,LOOPBACK,RUNNING,MULTICAST,TCPCKSUM> mtu 8160</P><P>        inet 127.0.0.1 netmask-or-prefix 0xff000000 broadcast 127.0.0.1</P><P>        ether 00:00:00:00:00:00 (VIA Provider)</P><P>vif1: flags=0xa2d08863<BROADCAST,RUNNING,MULTICAST,TCPCKSUM,VLAN> mtu 1500</P><P>        ether 02:a0:98:29:45:4a (Enabled virtual interface)</P><P>vif1-20: flags=0x2948863<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500</P><P>        inet 192.168.1.33 netmask-or-prefix 0xffffff00 broadcast 192.168.1.255</P><P>        ether 02:a0:98:29:45:4a (Enabled virtual interface)</P><P>WENETAPP2> vlan add vif1 30</P><P>vlan: vif1-30 has been created</P><P>WENETAPP2></P><P>WENETAPP2> ifconfig vif1-30 192.168.1.47</P><P>WENETAPP2> ifconfig -a</P><P>e0M: flags=0x2108866<BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500</P><P>        ether 00:a0:98:29:45:4a (auto-unknown-cfg_down) flowcontrol full</P><P>e0a: flags=0x8ad08867<BROADCAST,RUNNING,MULTICAST,TCPCKSUM,VLAN> mtu 1500</P><P>        ether 02:a0:98:29:45:4a (auto-1000t-fd-up) flowcontrol full</P><P>        trunked vif1</P><P>e0b: flags=0x8ad08867<BROADCAST,RUNNING,MULTICAST,TCPCKSUM,VLAN> mtu 1500</P><P>        ether 02:a0:98:29:45:4a (auto-1000t-fd-up) flowcontrol full</P><P>        trunked vif1</P><P>lo: flags=0x1948049<UP,LOOPBACK,RUNNING,MULTICAST,TCPCKSUM> mtu 8160</P><P>        inet 127.0.0.1 netmask-or-prefix 0xff000000 broadcast 127.0.0.1</P><P>        ether 00:00:00:00:00:00 (VIA Provider)</P><P>vif1: flags=0xa2d08863<BROADCAST,RUNNING,MULTICAST,TCPCKSUM,VLAN> mtu 1500</P><P>        ether 02:a0:98:29:45:4a (Enabled virtual interface)</P><P>vif1-20: flags=0x2948863<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500</P><P>        inet 192.168.1.33 netmask-or-prefix 0xffffff00 broadcast 192.168.1.255</P><P>        ether 02:a0:98:29:45:4a (Enabled virtual interface)</P><P>vif1-30: flags=0x2948863<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500</P><P>        inet 192.168.1.47 netmask-or-prefix 0xffffff00 broadcast 192.168.1.255</P><P>        ether 02:a0:98:29:45:4a (Enabled virtual interface)</P><P>WENETAPP2> ifconfig vif1 nfo</P><P>ifconfig: invalid option 'nfo' on a physical VLAN interface</P><P>usage: "ifconfig ?" will list the accepted subcommands and arguments</P><P>WENETAPP2></P><P></P><P>Any ideas ?</P><P></P><P>thanks and regards </P><P></P><P>Jack </P></BODY></HTML> Wed, 30 Nov 2011 17:03:21 GMT https://community.netapp.com/t5/ONTAP-Discussions/vif-has-nfo-enabled-can-t-add-new-vlan/m-p/41512#M9768 jack_quinn 2011-11-30T17:03:21Z Re: vif has nfo enabled, can't add new vlan https://community.netapp.com/t5/ONTAP-Discussions/vif-has-nfo-enabled-can-t-add-new-vlan/m-p/41515#M9769 <HTML><HEAD></HEAD><BODY><DIV><P>So with vlans it looks like nfo is per vlan ifconfig only. Unless ontap 8 and there is an ip on the base I tagged vif. </P></DIV></BODY></HTML> Wed, 30 Nov 2011 20:21:32 GMT https://community.netapp.com/t5/ONTAP-Discussions/vif-has-nfo-enabled-can-t-add-new-vlan/m-p/41515#M9769 scottgelb 2011-11-30T20:21:32Z Re: vif has nfo enabled, can't add new vlan https://community.netapp.com/t5/ONTAP-Discussions/vif-has-nfo-enabled-can-t-add-new-vlan/m-p/41519#M9770 <HTML><HEAD></HEAD><BODY><P>Cheers Scott,</P><P></P><P>Only saw this now, yeas, it looks like that alright, </P><P>I shall investigate further next oppertunity i get </P><P>thanks & regards </P><P></P><P>Jack </P></BODY></HTML> Fri, 13 Jan 2012 11:49:22 GMT https://community.netapp.com/t5/ONTAP-Discussions/vif-has-nfo-enabled-can-t-add-new-vlan/m-p/41519#M9770 jack_quinn 2012-01-13T11:49:22Z Re: vif has nfo enabled, can't add new vlan https://community.netapp.com/t5/ONTAP-Discussions/vif-has-nfo-enabled-can-t-add-new-vlan/m-p/41524#M9771 <HTML><HEAD></HEAD><BODY><P>Each time, I have to ad VLAN on nfo interface, I do that.</P><P>I'm working on DoT 8.1 GA and NFO is set on the vif not per VLAN.</P></BODY></HTML> Fri, 22 Jun 2012 05:07:31 GMT https://community.netapp.com/t5/ONTAP-Discussions/vif-has-nfo-enabled-can-t-add-new-vlan/m-p/41524#M9771 ds 2012-06-22T05:07:31Z Re: vif has nfo enabled, can't add new vlan https://community.netapp.com/t5/ONTAP-Discussions/vif-has-nfo-enabled-can-t-add-new-vlan/m-p/41528#M9772 <HTML><HEAD></HEAD><BODY><DIV><P>Nfo can be applied to any interface you ifconfig. If the base Ifgrp then it won't apply to a vlan on that Ifgrp unless the vlan ifconfig has nfo. The base ifgrp is a different logical interface than the vlan. Apply nfo to any/every interface you want failover to occur on. Then make sure the options is set to any_nic or all_nics if you want all interfaces with nfo to have to fail or just one for the failover to occur. </P></DIV></BODY></HTML> Fri, 22 Jun 2012 05:16:49 GMT https://community.netapp.com/t5/ONTAP-Discussions/vif-has-nfo-enabled-can-t-add-new-vlan/m-p/41528#M9772 scottgelb 2012-06-22T05:16:49Z Re: vif has nfo enabled, can't add new vlan https://community.netapp.com/t5/ONTAP-Discussions/vif-has-nfo-enabled-can-t-add-new-vlan/m-p/41533#M9773 <HTML><HEAD></HEAD><BODY><P>I'm interested in reading what NFO can do on a VLAN basis.</P><P>DoT can detect an issue on VLAN configuration like the loss of a VLAN into a trunk?</P><P>I put on the ifgrp because I know that on this particular interface, if something goes really wrong, I want to takeover.</P></BODY></HTML> Fri, 22 Jun 2012 05:21:43 GMT https://community.netapp.com/t5/ONTAP-Discussions/vif-has-nfo-enabled-can-t-add-new-vlan/m-p/41533#M9773 ds 2012-06-22T05:21:43Z