Before you begin—In this scenario, we will deploy three VRF instances, MyVRF-50016, MyVRF-50018, and MyVRF-50019 on the border leafs BL-1 and BL-2 in 9K-FABRIC. You should ensure that you have already deployed the corresponding network(s) on the fabric's leaf switches.
After deploying one network on the leaf switches, you will have to deploy the associated VRF on the border leafs so that the
network(s) can be extended from/to the 9K-FABRIC. To know how to create a fabric, and networks and VRFs, see the Control chapter in the Cisco DCNM LAN Fabric User Guide, Release 11.0(1).
In the Select a Fabric page, ensure that you select 9K-FABRIC in the drop-down box and click Continue (at the top right part of the screen). After clicking Continue, the Networks page comes up.
Click on VRF View. The VRFs page comes up.
We will deploy 3 new VRF instances MyVRF-50016, MyVRF-50018, and MyVRF-50019 on the border leafs. To do that, select the checkboxes (in the extreme left column).
Click the Continue button at the top right part of the screen. The VRF Deployment page (Topology View) comes up. You can deploy VRFs on multiple
switches simultaneously, but with the same role. So, deploy the selected VRFs on the border leafs.
Note |
In the image, you can see that the VRF instances are deployed on the leaf switches (green color indicates deployed status).
Note that the color code, and hence the deployment state on switches is contextual and specific to the selection. In this
scenario, the deployed state only depicts that the 3 selected VRFs are deployed on leaf switches LEAF3, LEAF1 and LEAF2. It
does not display information about other VRF deployment instances, if any.
|
Select the multi-select check box from the panel of options available (Step 1 in the image).
Then, click your mouse (or track pad) and drag the cursor across BL-1 and BL-2 (Step 2 in the image).
Immediately, the Switches Deploy screen (for VRFs) appears. A tab is displayed for each VRF.
Click the checkbox next to the Switch column. Both the border leaf check boxes will be selected automatically. Alternatively, you can select check boxes next to
the switches.
Click on NONE in the Extend column, select VRF_LITE and click on the Save button below it.
Repeat this action for the second row too. A sample screenshot:
This creates a VRF Lite extension for this VRF, as seen in the Extension Details section that appears at the bottom part of the screen.
In the Extension Details section, select the Source Switch checkbox (or ensure that you select the check box in each row). This is how the screen looks when you select both the switches
in the Extension Details section.
The corresponding dot1Q tag for the VRF is auto-populated in the DOT1Q_ID field.
Now, select the MyVRF_50018 and MyVRF_50019 and similarly update relevant parameters.
Click the Save button at the bottom right part of the Switches Deploy screen to save all VRFs' configurations on the selected switches.
The VRF Deployment screen (Topology view) appears.
BL-1 and BL-2 icons will be displayed in blue color, indicating that a deployment is pending. If you want to check your configurations,
click on the Preview (eye) icon.
You can select a switch and a VRF to view corresponding configurations. Configuration details of MyVRF_5016 that is pushed to BL-1 are included in the Appendix section.
After you verify that the configurations that are generated from the profiles are correct for the selected switches, click
the Deploy button (on the top right part of the Topology View screen) to deploy the MyVRF_50016, MyVRF_50018, and MyVRF_50019 VRF configurations on BL-1 and BL-2.
DCNM shows the deployment status in the topology by highlighting the switch icons with different colors, yellow for In Progress,
green for Deployed, and red for Out of sync status.
When the switch icons turn green, it indicates that the MyVRF_50016, MyVRF_50018, and MyVRF_50019 VRF configurations have been deployed on the border leafs of the 9K-FABRIC. You can also click the Detailed View option to see the status.
After configurations in 9K-FABRIC are complete, you should enable configurations in Fabric2 too.