Hello;
FAS2050 running with ONTAP 7.3.5.
If we set cf.takeover.on_network_interface_failure to "on" and the failure policy to "any_nic", and network connectivity is _lost_ on a partner-configured NIC (but the NIC hasn't necessarily "failed"), is this sufficient to trigger a takeover?
We had a situation today where a patch panel or switch issue caused one of the NICs to trigger a "Link down". We didn't have the network interface failure takeover option configured, but I am wondering if this could have saved us.
Thanks, Ray
You also need the nfo option in the ifconfig command for the interfaces you want trigger the failover. See the man pages for ifconfig and options cf.takeover.on_network_interface_* and the Active-Active Config Guide.
But why not create a vif (now called interface group) and if you need two networks, use VLAN tags?
vif create multi blah e0a e0b #lacp would be better than multi vlan create blah 10 20 ifconfig blah-10 1.2.3.4 netmask 255.255.255.0 mtusize 9000 partner blah-10 ifconfig blah-20 5.6.7.8 netmask 255.255.255.0 mtusize 9000 partner blah-20
You need your switch ports set up for link aggregation/port channel/EtherChannel and VLAN tagging allowing the VLANs you want.
Share and enjoy!
Peter
-----Original Message----- From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Ray Van Dolson Sent: Wednesday, November 21, 2012 12:53 PM To: toasters@teaparty.net Subject: cf.takeover.on_network_interface_failure question
Hello;
FAS2050 running with ONTAP 7.3.5.
If we set cf.takeover.on_network_interface_failure to "on" and the failure policy to "any_nic", and network connectivity is _lost_ on a partner-configured NIC (but the NIC hasn't necessarily "failed"), is this sufficient to trigger a takeover?
We had a situation today where a patch panel or switch issue caused one of the NICs to trigger a "Link down". We didn't have the network interface failure takeover option configured, but I am wondering if this could have saved us.
Thanks, Ray _______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
On Wed, Nov 21, 2012 at 09:57:53PM +0000, Learmonth, Peter wrote:
You also need the nfo option in the ifconfig command for the interfaces you want trigger the failover. See the man pages for ifconfig and options cf.takeover.on_network_interface_* and the Active-Active Config Guide.
But why not create a vif (now called interface group) and if you need two networks, use VLAN tags?
vif create multi blah e0a e0b #lacp would be better than multi vlan create blah 10 20 ifconfig blah-10 1.2.3.4 netmask 255.255.255.0 mtusize 9000 partner blah-10 ifconfig blah-20 5.6.7.8 netmask 255.255.255.0 mtusize 9000 partner blah-20
You need your switch ports set up for link aggregation/port channel/EtherChannel and VLAN tagging allowing the VLANs you want.
Share and enjoy!
Peter
Thanks for the response, Peter.
In our case, this particular 2050C has its expansion slot used by a SAS card (I can't remember now if it has only one or two expansion slots -- but we do not have any available), so we're limited to the two onboard NICs. One NIC is headed off to a separate switch to provide back-end storage connectivity to a legacy environment that doesn't hang off the main, core switch.
The other ports uplink to our core.
In an ideal world we'd be able to vif these but can't (easily) without some infrastrcuture changes, so using "nfo" and the nic failover options will be useful for us to bridge the gap.
Ray
-----Original Message----- From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Ray Van Dolson Sent: Wednesday, November 21, 2012 12:53 PM To: toasters@teaparty.net Subject: cf.takeover.on_network_interface_failure question
Hello;
FAS2050 running with ONTAP 7.3.5.
If we set cf.takeover.on_network_interface_failure to "on" and the failure policy to "any_nic", and network connectivity is _lost_ on a partner-configured NIC (but the NIC hasn't necessarily "failed"), is this sufficient to trigger a takeover?
We had a situation today where a patch panel or switch issue caused one of the NICs to trigger a "Link down". We didn't have the network interface failure takeover option configured, but I am wondering if this could have saved us.
Thanks, Ray