Enabling the DvR-leaf-mode boot flag before you configure a node as a DvR Leaf, automatically removes all existing non-DvR configuration on the node such as platform VLANs and their IP address configuration, CLIP configuration, routing protocol configuration and VRF configuration. The gateway IPv4 address, if configured, is also removed.
You cannot configure SPB-PIM GW on a Leaf node. The configuration is supported only on a DvR Controller.
You cannot perform Layer 3 configuration (for example, IP interfaces, IP routing, and VRFs). You can only perform Layer 2 configuration.
You cannot configure Microsoft NLB on a Leaf node.
You cannot configure Fabric Extend on a Leaf node.
You cannot configure the VXLAN Gateway on a Leaf node.
You cannot configure a T-UNI on a Leaf node.
You cannot configure IPv4 multicast on a Leaf node. The configuration is supported only on a DvR Controller.
You can configure only one instance of vIST on a Leaf node pair. Also, you cannot configure vIST on Leaf nodes from different domains.
Platform VLANs are not supported. You cannot configure a platform VLAN directly on a DvR leaf node. However, you can configure a VLAN Management Instance on a DvR leaf node. After you configure the management VLAN, you can configure a platform VLAN.
You cannot configure IP Shortcuts and IP Multicast over Fabric Connect on Leaf nodes. This configuration is pushed from the DvR Controllers in the domain.
You must manually configure an I-SID on a Layer 2 VSN Leaf node. This configuration is not pushed from a DvR Controller.
DvR-enabled VLAN/I-SIDs are for host connectivity only; you cannot connect a router to a DvR-enabled VLAN/I-SID and use dynamic or static routing. Use a non-DvR VLAN/I-SID instead to connect an external router.