ONTAP Discussions
ONTAP Discussions
Hi,
Here are the relevant network configurations that have been sanitized for netapp1 and netapp2, the two cluster members.
###
hostname netapp2
vif create lacp -b ip Multi3 e0a e0c e1a e1c e4a e4c
vif create lacp -b ip Multi4 e0b e0d e1b e1d e4b e4d
vif create single Single2 Multi3 Multi4
vif favor Multi4
vlan create Single2 101 102 103 104 105 106 107 108 109 110
ifconfig Single2-101 `hostname`-Single2-101 netmask 255.255.248.0 broadcast x.x.x.x mtusize 9000 -wins partner netapp1-Single1-101
ifconfig Single2-102 `hostname`-Single2-102 netmask 255.255.254.0 broadcast x.x.x.x mtusize 9000 -wins partner netapp1-Single1-102
ifconfig Single2-103 `hostname`-Single2-103 netmask 255.255.252.0 broadcast x.x.x.x mtusize 9000 -wins partner netapp1-Single1-103
ifconfig Single2-104 `hostname`-Single2-104 netmask 255.255.252.0 broadcast x.x.x.x mtusize 9000 -wins partner netapp1-Single1-104
ifconfig Single2-105 `hostname`-Single2-105 netmask 255.255.255.0 broadcast x.x.x.x mtusize 9000 -wins partner netapp1-Single1-105
ifconfig Single2-106 `hostname`-Single2-106 netmask 255.255.255.0 broadcast x.x.x.x mtusize 9000 -wins partner netapp1-Single1-106
ifconfig Single2-107 `hostname`-Single2-107 netmask 255.255.255.0 broadcast x.x.x.x mtusize 9000 -wins partner netapp1-Single1-107
ifconfig Single2-108 `hostname`-Single2-108 netmask 255.255.224.0 broadcast x.x.x.x mtusize 9000 -wins partner netapp1-Single1-108
ifconfig Single2-109 `hostname`-Single2-109 netmask 255.255.252.0 broadcast x.x.x.x mtusize 9000 -wins partner netapp1-Single1-109
ifconfig Single2-110 `hostname`-Single2-110 netmask 255.255.252.0 broadcast x.x.x.x mtusize 9000 -wins partner netapp1-Single1-110
route add default 10.10.10.10
Hey All,
NetApp support opened RFE 488056 for this issue. It is worth noting that this outage was caused by a faulty line card and not a configuration snafu. It could happen to you if you use LACP in your environment.
For now, it appears that single interfaces are resilient to this failure mode because each filer tries to arp the other filer. Support told me that LACP links do _not_ arp back and forth and that is why we got bit. Once a LACP link establishes itself that's all the filer cares about in terms of the network health on that interface. It seems Ontap should go farther than that considering they do it with single links already.
-Brian