topic Re: Failover Group Join Error in ONTAP Discussions https://community.netapp.com/t5/ONTAP-Discussions/Failover-Group-Join-Error/m-p/137521#M30327 <P>Great to know - for anyone else who comes across this - failover-groups were very important in 8.1/8.2, but 8.3 introduces broadcast domains that essentially do the same thing, so your aim would be to add the port to the broadcast domain instead.</P> Tue, 23 Jan 2018 07:33:26 GMT AlexDawson 2018-01-23T07:33:26Z Failover Group Join Error https://community.netapp.com/t5/ONTAP-Discussions/Failover-Group-Join-Error/m-p/137495#M30325 <P>Can anyone help me identify what the issue is here and profer the solution? Thanks.</P><P>&nbsp;</P><P>&nbsp;</P><P>Cluster_node::&gt; net interface failover-groups add-targets -vserver Cluste_node -failover-group 136.171.211.0/24 -targets Node3:a0a-3170<BR />&nbsp; (network interface failover-groups add-targets)</P><P><FONT color="#ff0000"><STRONG>Error: command failed: Failover group "136.171.211.0/24" cannot be modified because it is automatically generated by broadcast domain "136.171.211.0/24".</STRONG></FONT></P><P>&nbsp;</P><P>&nbsp;</P><P>Cluster_node::&gt; net int failover-groups show<BR />&nbsp; (network interface failover-groups show)<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Failover<BR />Vserver&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Group&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Targets<BR />---------------- ---------------- --------------------------------------------<BR />Cluster<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Cluster<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Node4:e0c, Node4:e0e, Node3:e0c, Node3:e0e,<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Node1:e1a, Node1:e2a, tito:e1a,<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; tito:e2a<BR />Cluster_node<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 136.171.211.0/24<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Node4:a0a-211, Node3:a0a-211,<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Node1:a0a-211, Node1:a0a-3170,<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; tito:a0a-211, tito:a0a-3170<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 136.171.87.0/24<BR />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Node1:a0a-1187, tito:a0a-1187</P> Wed, 04 Jun 2025 14:07:37 GMT https://community.netapp.com/t5/ONTAP-Discussions/Failover-Group-Join-Error/m-p/137495#M30325 COG 2025-06-04T14:07:37Z Re: Failover Group Join Error https://community.netapp.com/t5/ONTAP-Discussions/Failover-Group-Join-Error/m-p/137500#M30326 <P>I have reolved the problem.</P> Mon, 22 Jan 2018 17:50:53 GMT https://community.netapp.com/t5/ONTAP-Discussions/Failover-Group-Join-Error/m-p/137500#M30326 COG 2018-01-22T17:50:53Z Re: Failover Group Join Error https://community.netapp.com/t5/ONTAP-Discussions/Failover-Group-Join-Error/m-p/137521#M30327 <P>Great to know - for anyone else who comes across this - failover-groups were very important in 8.1/8.2, but 8.3 introduces broadcast domains that essentially do the same thing, so your aim would be to add the port to the broadcast domain instead.</P> Tue, 23 Jan 2018 07:33:26 GMT https://community.netapp.com/t5/ONTAP-Discussions/Failover-Group-Join-Error/m-p/137521#M30327 AlexDawson 2018-01-23T07:33:26Z Re: Failover Group Join Error https://community.netapp.com/t5/ONTAP-Discussions/Failover-Group-Join-Error/m-p/139849#M30901 <P>Thanks. Can you help with this question?</P> <P>&nbsp;</P> <P><A href="https://community.netapp.com/t5/Data-ONTAP-Discussions/Cluster-Configuration/m-p/139848" target="_blank">https://community.netapp.com/t5/Data-ONTAP-Discussions/Cluster-Configuration/m-p/139848</A></P> <P>&nbsp;</P> Wed, 25 Apr 2018 22:24:07 GMT https://community.netapp.com/t5/ONTAP-Discussions/Failover-Group-Join-Error/m-p/139849#M30901 COG 2018-04-25T22:24:07Z