Broadcast Domains and Failover Groups (new version)

[@TheseWhiteNights]

Hi Neil, I just want to say thank you for putting these videos together. I am on a project replacing a FAS8040 with an AFF device (not sure yet which model). I don't trust the legacy configuration, so I am spiking on how this is actually supposed to be set up. Your videos are incredibly helpful in breaking down concepts I don't understand from the NetApp docs. Thanks again!

[@Flackbox]

Thanks for the kind words. I'm happy to help!

[@kfiresmith]

Hi Neil, around 9m, you say to add interfaces that are part of an interface group to a bcast domain first then add the ifgrp to the bcast domain, but that isn't correct as interfaces that are part of an ifgrp cannot be in a bcast domain. You have to remove ifaces from their bcast domain prior to adding them to an ifgrp.

[@krzysztofelektryczny8206]

Question regarding ipspace and broadcast domain. - What is a purpose of creating object( ipspace ) which is able to contain only one object ( broadcast domain ) ? If ip space ( layer 3) coud be able to contain multiple broadcast domains ( layer 2) and allow to route between them and at the same time was able to sepatate it from diffirent ipspace which coud have identical configuration ( same subnet ) - that would be logic. Now its just unnecessary layer. You could name broadcast domains as IPspace and separate traffic between them - the same story. The point is that purpose of creating object is ability to group multiple objects . Here we have one object able to store only one object - pointless.