Hi,
One of our customers has enabled network failover on 2nd level vifs for their cluster,
When trying to add a new vlan, they are getting error below
nbg2-fas13> vlan add fas13-2ndLvl01 316
vlan: Create failed. Negotiated failover is enabled on interface fas13-2ndLvl01.
nbg2-fas13> ifconfig -a
e0a: flags=0x8af0c867<BROADCAST,RUNNING,MULTICAST,TCPCKSUM,VLAN> mtu 1500
ether 02:1b:21:a8:22:e0 (auto-1000t-fd-up) flowcontrol full
trunked cra03-1stLvl01
e0b: flags=0x8af0c867<BROADCAST,RUNNING,MULTICAST,TCPCKSUM,VLAN> mtu 1500
ether 02:1b:21:a8:22:e0 (auto-1000t-fd-up) flowcontrol full
trunked cra03-1stLvl01
e1a: flags=0x8af0c867<BROADCAST,RUNNING,MULTICAST,TCPCKSUM,VLAN> mtu 1500
ether 02:1b:21:a8:22:e0 (auto-1000t-fd-up) flowcontrol full
trunked cra04-1stLvl02
e1b: flags=0x8af0c867<BROADCAST,RUNNING,MULTICAST,TCPCKSUM,VLAN> mtu 1500
ether 02:1b:21:a8:22:e0 (auto-1000t-fd-up) flowcontrol full
trunked cra04-1stLvl02
e1c: flags=0x274c867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500
inet 192.168.1.13 netmask 0xffffff00 broadcast 192.168.1.255
ether 00:1b:21:a8:22:e2 (auto-unknown-down) flowcontrol full
e1d: flags=0x270c866<BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500
ether 00:1b:21:a8:22:e3 (auto-unknown-down) flowcontrol full
c0a: flags=0x1f4c867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 9000 PRIVATE
inet 192.168.1.183 netmask 0xffffff00 broadcast 192.168.1.255
ether 00:a0:98:17:6c:ba (auto-10g_twinax-fd-up) flowcontrol full
c0b: flags=0x1f4c867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 9000 PRIVATE
inet 192.168.2.79 netmask 0xffffff00 broadcast 192.168.2.255
ether 00:a0:98:17:6c:bb (auto-10g_twinax-fd-up) flowcontrol full
e0M: flags=0x2b4c867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500
inet 192.168.192.209 netmask 0xffffff00 broadcast 192.168.192.255
partner e0M (not in use)
ether 00:a0:98:17:6c:bc (auto-100tx-fd-up) flowcontrol full
e0P: flags=0x2b4c867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 PRIVATE
inet 192.168.0.207 netmask 0xfffffc00 broadcast 192.168.3.255 noddns
ether 00:a0:98:17:6c:bd (auto-100tx-fd-up) flowcontrol full
lo: flags=0x1b48049<UP,LOOPBACK,RUNNING,MULTICAST,TCPCKSUM> mtu 8160
inet 127.0.0.1 netmask 0xff000000 broadcast 127.0.0.1
ether 00:00:00:00:00:00 (RNIC Provider)
losk: flags=0x40a400c9<UP,LOOPBACK,RUNNING> mtu 9188
inet 127.0.20.1 netmask 0xff000000 broadcast 127.0.20.1
cra03-1stLvl01: flags=0xaaf0c863<BROADCAST,RUNNING,MULTICAST,TCPCKSUM,VLAN> mtu 1500
ether 02:1b:21:a8:22:e0 (Enabled interface groups)
trunked fas13-2ndLvl01
cra04-1stLvl02: flags=0xaaf0c863<BROADCAST,RUNNING,MULTICAST,TCPCKSUM,VLAN> mtu 1500
ether 02:1b:21:a8:22:e0 (Enabled interface groups)
trunked fas13-2ndLvl01
fas13-2ndLvl01: flags=0xa2f0c863<BROADCAST,RUNNING,MULTICAST,TCPCKSUM,VLAN> mtu 1500
partner fas14-2ndLvl01 (not in use)
ether 02:1b:21:a8:22:e0 (Enabled interface groups)
nfo enabled
fas13-2ndLv-301: flags=0x6b4c863<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM,NOWINS> mtu 1500
inet 192.168.193.53 netmask 0xffffffc0 broadcast 192.168.193.63
partner inet 192.168.193.54 (not in use)
ether 02:1b:21:a8:22:e0 (Enabled interface groups)
fas13-2ndLv-631: flags=0x6b4c863<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM,NOWINS> mtu 1500
inet 192.168.203.71 netmask 0xffffffc0 broadcast 192.168.203.127
partner inet 192.168.203.72 (not in use)
ether 02:1b:21:a8:22:e0 (Enabled interface groups)
fas13-2ndLv-601: flags=0x6b4c863<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM,NOWINS> mtu 1500
inet 192.168.200.135 netmask 0xffffff80 broadcast 192.168.200.255
partner inet 192.168.200.136 (not in use)
ether 02:1b:21:a8:22:e0 (Enabled interface groups)
fas13-2ndLv-641: flags=0x6b4c863<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM,NOWINS> mtu 1500
inet 192.168.204.135 netmask 0xffffff80 broadcast 192.168.204.255
partner inet 192.168.204.136 (not in use)
ether 02:1b:21:a8:22:e0 (Enabled interface groups)
fas13-2ndLv-650: flags=0x6b4c863<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM,NOWINS> mtu 1500
inet 192.168.205.3 netmask 0xffffffe0 broadcast 192.168.205.31
partner inet 192.168.205.4 (not in use)
ether 02:1b:21:a8:22:e0 (Enabled interface groups)
nbg2-fas13>
nbg2-fas13> rdfile /etc/rc
#Regenerated by registry Mon Nov 14 12:21:20 UTC 2011
#Auto-generated by setup Tue Sep 20 10:54:08 UTC 2011
hostname nbg2-fas13
ifgrp create multi cra03-1stLvl01 -b ip e0a e0b
ifgrp create multi cra04-1stLvl02 -b ip e1a e1b
ifgrp create single fas13-2ndLvl01 cra04-1stLvl02 cra03-1stLvl01
ifconfig fas13-2ndLv-301 192.168.193.53 netmask 255.255.255.192 mtusize 1500 -wins partner 192.168.193.54
ifconfig fas13-2ndLv-631 192.168.203.71 netmask 255.255.255.192 mtusize 1500 -wins partner 192.168.203.72
ifconfig fas13-2ndLv-601 192.168.200.135 netmask 255.255.255.128 mtusize 1500 -wins partner 192.168.200.136
ifconfig fas13-2ndLv-641 192.168.204.135 netmask 255.255.255.128 mtusize 1500 -wins partner 192.168.204.136
ifconfig fas13-2ndLv-650 192.168.205.3 netmask 255.255.255.224 mtusize 1500 -wins partner 192.168.205.4
ifconfig fas13-2ndLvl01 mediatype auto partner fas14-2ndLvl01
ifconfig e0M `hostname`-e0M flowcontrol full partner e0M
ifconfig e1c `hostname`-e1c mediatype auto flowcontrol full
ifconfig fas13-2ndLvl01 nfo
route add default 192.168.193.1 1
route add net 192.168.225/27 192.168.205.1 1
routed on
options dns.domainname lan.gasp2.newbay.com
options dns.enable on
options nis.enable off
savecore
Do you think we could disable nfo, add new vlan, and then re-enable nfo ?
nbg2-fas13> ifconfig fas13-2ndLvl01 -nfo
nbg2-fas13> vlan add fas13-2ndLvl01 316
nbg2-fas13> ifconfig fas13-2ndLvl01 nfo
Thanks and regards
Jack
