Clustered Data ONTAP (cDOT) is NetApp’s newest storage operating system. Essentially, it takes all the goodness of ONTAP operating in 7-Mode and tethers it together into a clustered environment. This allows seamless scalability, non-disruptive upgrades of software and hardware and flexibility in storage provisioning.
One area of IT where this is especially useful is in a multi-tenant environment. With cDOT, storage administrators can segment storage to users much like virtual machines in an ESX farm. You share the same physical resources, but you abstract the storage layer via virtualized storage instances known as Storage Virtual Machines (SVMs).
Prior to cDOT 8.3, providing true multi-tenancy had some limitations.
- Each LIF had to have a unique IP address in the cluster.
- In some cases, LIFs could end up on ports that were not on the name network as the LIF, even with failover groups properly defined (such as mistakenly migrating a LIF manually).
- LIFs could end up on ports that had different MTU sizes than their original source ports.
cDOT 8.3 solved those problems with the addition of Broadcast Domains and IP spaces.
Broadcast Domains and…. Roomba?
The easiest way to think of a broadcast domain is to think of a Roomba.
Roombas are cute little robots that can be programmed to “know” your room. They sense walls, furniture and other obstacles to avoid as they clean. If you wanted your Roomba to clean only your bedroom, you would stick the Roomba in there and shut the door. The walls and door would keep the Roomba confined to where it belongs.
However, if you left the door open, the Roomba could eventually find its way out and start cleaning the rest of your house. If one room had, say, super high shag carpeting, the Roomba might get stuck and you get a ROOMBA OUTAGE!
Read more at DataCenterDude.com!