topic Re: FAS2040-R5 LACP VIF issue between controllers in Network and Storage Protocols https://community.netapp.com/t5/Network-and-Storage-Protocols/FAS2040-R5-LACP-VIF-issue-between-controllers/m-p/18268#M1625 <HTML><HEAD></HEAD><BODY><P>The solution of course was a simple one (as it usually is). The network engineer had port e0d from each controller go to a different switch from ports e0b and e0c. This of course created the issue. I recreated the VIFs to only use e0b and e0c for the time being until I am able to stop by the datacenter and manually switch each cable to its corresponding port in the correct switch. </P></BODY></HTML> Mon, 24 Jan 2011 11:38:49 GMT cserpadss 2011-01-24T11:38:49Z FAS2040-R5 LACP VIF issue between controllers https://community.netapp.com/t5/Network-and-Storage-Protocols/FAS2040-R5-LACP-VIF-issue-between-controllers/m-p/18263#M1624 <HTML><HEAD></HEAD><BODY><P>Hello I am having a very odd problem. I am setting up 2 controllers, each with its own VIF to export NFS volumes. Each controller is active/active and should be reachable on its own. The issue is that only one controller seems to be able to have an active LACP VIF at a time, otherwise if I destroy the VIF and assign individual IPs to each NIC I can reach them. When ctrlA is up and pingable the other ctrl (B) reports all links down and isn't reachable. But if I reboot ctrlA, ctrlB's VIF comes up and then it's reachable but then ctrlA reports all of its links are down and can't be reached! Below are the specs:</P><P></P><P>ctrlA e0a (management) connects to SW-A (management/data Cisco 3560G switch), subnet 10.1.100/24</P><P>ctrlA e0b,e0c,e0d (NFS) connect as an LACP VIF: (Lvif1: 3 links, transmit 'IP Load balancing', VIF Type 'lacp' fail 'default') to SW-B (storage comm only Cisco 3560G switch which is trunked to SW-C)</P><P></P><P>ctrlA e0a (management) connects to SW-A (management/data Cisco 3560G switch), subnet 10.1.100/24</P><P>ctrlA e0b,e0c,e0d (NFS) connect as an LACP VIF: (Lvif1: 3 links, transmit 'IP Load balancing', VIF Type 'lacp' fail 'default') to SW-C (storage comm only Cisco 3560G switch which is trunked to SW-B)</P><P></P><P>Both switch B and C are using IP based load balancing (not MAC).</P><P></P><P>In both switches LACP is enabled on each port connecting to the controllers (mode active).</P><P></P><P>In both switches a channel group was created for each controller.</P><P></P><P>Any ideas ?</P></BODY></HTML> Thu, 05 Jun 2025 07:01:43 GMT https://community.netapp.com/t5/Network-and-Storage-Protocols/FAS2040-R5-LACP-VIF-issue-between-controllers/m-p/18263#M1624 cserpadss 2025-06-05T07:01:43Z Re: FAS2040-R5 LACP VIF issue between controllers https://community.netapp.com/t5/Network-and-Storage-Protocols/FAS2040-R5-LACP-VIF-issue-between-controllers/m-p/18268#M1625 <HTML><HEAD></HEAD><BODY><P>The solution of course was a simple one (as it usually is). The network engineer had port e0d from each controller go to a different switch from ports e0b and e0c. This of course created the issue. I recreated the VIFs to only use e0b and e0c for the time being until I am able to stop by the datacenter and manually switch each cable to its corresponding port in the correct switch. </P></BODY></HTML> Mon, 24 Jan 2011 11:38:49 GMT https://community.netapp.com/t5/Network-and-Storage-Protocols/FAS2040-R5-LACP-VIF-issue-between-controllers/m-p/18268#M1625 cserpadss 2011-01-24T11:38:49Z