New and Changed Information

The following table provides an overview of the significant changes to the organization and features in this guide up to this current release. The table does not provide an exhaustive list of all changes made to the guide or of the new features up to this release.

Table 1. New Features and Changed Behavior

Feature or Change

Description

Where Documented

Initial release of document

Initial release of document.

Support for Multiple VRFs Under Single VNet

Beginning with Release 5.1(2), the ability to carve out multiple VRFs has been extended beyond the infra VNet so that you can divide any VNet into multiple VRFs under the same tenant, where multiple VRFs can exist in a single VNet. This is useful for situations such as cloud service access, where you might want to carve out multiple networks (VRFs) within a given VNet, allowing you to have separate routing by having unique route tables for each VRF within the VNet in the cloud.

The following graphic shows an example manged object (MO) relationship tree with multiple VRFs under the same tenant (VNet).

Figure 1.

In this example, two VRFs exist under the same tenant (VNet):

  • The primary VRF with the name mainVRF

  • A secondary VRF with the name servicesVRF

A second CIDR block and subnet exists in the same cloud context profile, under the same tenant (VNet), but that second CIDR block and subnet is associated with the secondary VRF in that same VNet.

Configuring Multiple VRFs Under a Single VNet in Cisco ACI Multi-Site Orchestrator

The following procedures describe how to configure multiple VRFs under a single VNet to create the configuration that was described in Support for Multiple VRFs Under Single VNet, where two VRFs exist under the same tenant (VNet):

  • The primary VRF with the name mainVRF

  • A secondary VRF with the name servicesVRF

Before you begin

Procedure


Step 1

In the Cisco ACI Multi-Site Orchestrator, click on the template that you want to edit.

The main page for that templates appears.

Step 2

In the middle pane, scroll down to VRFs area.

Step 3

Configure the primary VRF.

  1. Click Add VRF to add the primary VRF.

    An Untitled VRF 1 box appears in the VRFs area.

  2. Click the Untitled VRF 1 box.

    The configuration information for that VRF appears in the right pane.

  3. Enter a name for the primary VRF (for example, mainVRF).

  4. Associate this VRF with a region (for example, centralus).

    From the ACI Multi-Site Orchestrator perspective, this is the tenant or VNet that your VRF is associated with.

  5. Configure the CIDR for the primary VRF.

    For example: 192.1.1.1/16

Step 4

Configure the secondary VRF.

  1. Click Add VRF to add the secondary VRF.

    An Untitled VRF 1 box appears in the VRFs area.

  2. Click the Untitled VRF 1 box.

    The configuration information for that VRF appears in the right pane.

  3. Enter a name for the secondary VRF (for example, servicesVRF).

    Note that you will not be associating this secondary VRF with a region. That's because this secondary VRF will be associated with region that is associated with the primary VRF.

Step 5

In the middle pane, click on the primary VRF again (mainVRF) .

The configuration information for the primary VRF appears in the right pane.

Step 6

Click on the region that is associated with the primary VRF (centralus).

The Update Cloud Region CIDRs window appears.

Step 7

Click Add CIDRs, then enter the CIDR information that will be used for the secondary VRF.

For example: 192.2.2.2/16

Step 8

Verify that the selection in the CIDR Type field is set to Secondary.

Step 9

In the Select Associated VRF field, choose Hosted VRF.

The VRF field appears.

Step 10

In the VRF field, choose the secondary VRF (servicesVRF).

Step 11

Enter subnet information, if necessary, then click Save.

The two CIDRs appear under the region in the primary VRF:

  • A first CIDR, which is associated with the primary VRF (mainVRF)

  • A second CIDR, which is associated with the secondary VRF (servicesVRF