How do failover groups work within broadcast domains to ensure performance during link failures?
Answered at 22:48 in Episode 414 - ONTAP Networking Updates - Fall 2026 · TechONTAPPodcast
How do failover groups work within broadcast domains to ensure performance during link failures?
Failover groups are constructs within a given broadcast domain that designate a subset of ports eligible to host a specific IP address. When a link fails or logical connectivity is lost, the IP address can move within the failover group to a port that still has proper connectivity to the network. This prevents situations such as a 100 gigabit interface failing over to a one gigabit interface, which would degrade performance. Failover groups leverage broadcast domain information to ensure graceful IP mobility.
Full answer and detailsRead the whole answer, key facts and every other question from this episode
In short
Failover groups are constructs within a given broadcast domain that designate a subset of ports eligible to host a specific IP address.
Richard Schefferniger, Solution Architect, EMEA and Latin America Region at NetApp · Episode 414 - ONTAP Networking Updates - Fall 2026 · TechONTAPPodcast · answer at 22:48
Key takeaways
- Failover groups are constructs within a given broadcast domain that designate a subset of ports eligible to host a specific IP address.
Quote to remember
“IP spaces or VRFs is the equivalent of your three yard fence, right? So it's much more hard to step over a three yard fence than it is over a one yard fence.”
— Richard Schefferniger
The full answer · about 1 min
Failover groups are constructs within a given broadcast domain that designate a subset of ports eligible to host a specific IP address. When a link fails or logical connectivity is lost, the IP address can move within the failover group to a port that still has proper connectivity to the network. This prevents situations such as a 100 gigabit interface failing over to a one gigabit interface, which would degrade performance. Failover groups leverage broadcast domain information to ensure graceful IP mobility.
Key facts
- VLANs introduced in networking technologies approximately 35 to 40 years ago
- IP spaces have been available in ONTAP since approximately version 8.0 to 9.0 releases
- CFM broadcast detection checks occur approximately every 10 minutes per port
- CFM broadcasts must fail twice in a row (approximately 30 minutes) before ONTAP detects broadcast domain fragmentation
- New TCP stack in ONTAP 9.19 delivers 3 to 4 times performance improvement for remote workers, sometimes even higher
People, companies and topics mentioned
More answers from this episode
- 3:00What are the main use cases for VLANs in ONTAP networking environments?
- 8:42How do IP spaces enable secure multi-tenancy in ONTAP systems?
- 14:18How does the bandwidth delay product optimization apply to long-distance SnapMirror replication in ONTAP?
- 18:18What TCP optimizations does ONTAP 9.19 provide for remote workers accessing SMB home shares?
- 23:06What is the CFM protocol and how does it improve broadcast domain detection in ONTAP?