上QQ阅读APP看书，第一时间看更新
How to do it...
- We start by going into the tenant we created in the previous recipe and going to Networking | Bridge Domains.
- Click on Actions, and then on Create Bridge Domain.
- This launches a new window. Here, we name our bridge domain and assign a VRF to it if we have already created one, or create a new VRF.
If we choose Create VRF, it brings up another window:
Because we have not created any timer policies for BGP or OSPF or a monitoring policy, we can leave these fields empty and use the default values.
- Once we click on SUBMIT, the new VRF is selected:
- We can set the forwarding to Optimize. Leave the End Point Retention Policy and IGMP Snoop Policy at the defaults, and click on NEXT to take us to the L3 Configurations window.
This is where we enable Unicast Routing and ARP flooding (if we want to), specify a MAC address and create a subnet.
ARP flooding is disabled by default. The fabric will convert any ARP broadcast traffic into unicast traffic and push it to the destination leaf node. If we want to enable traditional ARP flooding behavior, this is where we would enable it.
- To create a subnet, click on the plus sign, which brings up another window:
- Here, we specify the subnet and subnet mask for the network and set the scope to be private, public (Advertised Externally), or shared.
Private to VRF means that the subnet will not be advertised externally (outside of the VRF). Advertised Externally means just that, and will be flagged for advertising through a routing protocol to an external device. Shared between VRFs is similar to advertising externally, but is kept within the fabric. Because we are only concentrating on tenant A, at this stage, we will use the Private to VRF scope.
- Click on OK, which will take us back to the L3 Configurations window.
- Click on NEXT to take us to the final window, where we can select a monitoring policy.
- Click on FINISH.