DvR domains enable multi-site DvR deployments. Within a DvR domain, a set of up to eight DvR Controllers control the DvR domain Leaf switches. A domain can also include just DvR Controllers without DvR Leafs. Typically, a DvR domain is restricted to one physical location. Traffic leaving this physical location always passes through DvR Controllers.
A DvR domain is a logical group of switches or nodes that are DvR enabled. These nodes are not physically connected but are connected over the SPB Fabric such that each node is aware of the BMAC addresses of all other nodes within the domain. A DvR domain does not contain nodes that are not DvR enabled. However, those nodes can coexist with other DvR-enabled nodes within the same SPB Fabric network.
You configure a common DvR domain ID for all nodes belonging to a DvR domain. This domain ID translates internally to a Domain Data Distribution (DDD) I-SID. All switch nodes that share the same DvR domain ID or DDD I-SID receive the Layer 3 information that is distributed from all other nodes belonging to that DvR domain.
A DvR domain can contain multiple Layer 3 VSNs and Layer 2 VSNs. Layer 2 and Layer 3 VSNs can span multiple DvR domains.
A DvR domain typically has the following members:
DvR Controller(s)
DvR Leaf nodes
For more information about DvR Isolated Domains and Restrictions on a DvR Isolated Controller, see DvR Isolated Domains and Restrictions on a DvR Isolated Controller.
For scaling information on the number of Controllers and Leaf nodes to configure in a DvR domain, see Fabric Engine Release Notes.