Step 1

Log in to the Cisco Nexus Dashboard Orchestrator GUI.

Step 2

In the Main menu, select Infrastructure > Infra Configuration.

Step 3

In the top right of the main Infra Configuration view, click the Configure Infra button.

Step 4

In the left pane, under Sites, select a specific site.

Step 5

In the main window, click the Refresh button to discover any new or changed CSRs and regions.

Step 6

Finally, click Yes to confirm and load the connectivity information.

Step 7

Click Deploy to propagate the cloud site changes to other sites that have connectivity to it.

Step 1

Log in to the Cisco Nexus Dashboard Orchestrator GUI.

Step 2

In the Main menu, select Infrastructure > Infra Configuration.

Step 3

In the top right of the main pane, click Configure Infra.

Step 4

In the left pane, under Sites, select a specific cloud site.

Step 5

Provide Inter-Site Connectivity information.

1. In the right <Site> Settings pane, select the Inter-Site Connectivity tab.

2. In the Overlay Configuration area, enable the Multi-Site knob.

   This defines whether the overlay connectivity is established between this site and other sites.

3. (Optional) Specify the BGP Password.

1. In the Underlay Configuration area, click Add Connectivity.

2. From the Site dropdown, select the site to which you want to establish connectivity.

3. From the Connection Type dropdown, choose the type of connection between the sites.

   The following options are available:

   • Public Internet—connectivity between the two sites is established via the Internet.

     This type is supported between any two cloud sites or between a cloud site and an on-premises site.

   • Private Connection—connectivity is established using a private connection between the two sites.

     This type is supported between a cloud site and an on-premises site.

   • Cloud Backbone—connectivity is established using cloud backbone.

     This type is supported between two cloud sites of the same type, such as Azure-to-Azure or AWS-to-AWS.

   If you have multiple types of sites (on-premises, AWS, and Azure), different pairs of site can use different connection type.

4. (Optional) Enable IPsec.

   The following options are available:

   • For Public Internet connectivity, IPsec is always enabled.

   • For Cloud Backbone connectivity, IPsec is always disabled.

   • For Private Connection, you can choose to enable or disable IPsec.

5. If IPsec is enabled, choose the IKE Version for it.

   Internet Key Exchange (IKE) is a protocol used to establish security association for IPsec. You can choose which version of the protocol to use: IKEv1 (Version 1) or IKEv2 (Version 1) depending on your configuration.

6. Click Save to save the inter-site connectivity configuration.

   When you save connectivity information from Site1 to Site2, the reverse connectivity is automatically created from Site2 to Site1, which you can see by selecting the other site and checking the Underlay Configuration tab.

7. Repeat this step to add inter-site connectivity for other sites.

   When you establish underlay connectivity from Site1 to Site2, the reverse connectivity is done automatically for you.

   However, if you also want to establish inter-site connectivity from Site1 to Site3, you must repeat this step for that site as well.

Step 6

Provide External Connectivity information.

1. In the right <Site> Settings pane, select the External Connectivity tab.

2. Click Add External Connection.

   The Add External Connectivity dialog will open.

3. From the VRF dropdown, select the VRF you want to use for external connectivity.

   This is the VRF which will be used to leak the cloud routes. The Regions section will display the cloud regions that contain the CSRs to which this configuration be applied.

4. From the Name dropdown in the External Devices section, select the external device.

   This is the external device you added in the General Settings > External Devices list during general infra configuration and must already be defined as described in Configuring Infra: General Settings.

5. From the Tunnel IKE Version dropdown, pick the IKE version that will be used to establish the IPSec tunnel between the cloud site's CSRs and the external device.

6. (Optional) From the Tunnel Subnet Pool dropdown, choose one of the named subnet pools.

   Named subnet pool are used to allocate IP addresses for IPSec tunnels between cloud site CSRs and external devices. If you do not provide any named subnet pools here, the external subnet pool will be used for IP allocation.

   Providing a dedicated subnet pool for external device connectivity is useful for cases where a specific subnet is already being used to allocate IP addresses to the external router and you want to continue to use those subnets for IPSec tunnels for NDO and cloud sites.

   If you want to provide a specific subnet pool for this connectivity, it must already be created as described in Configuring Infra: General Settings.

7. (Optional) In the Pre-Shared Key field, provide the custom keys you want to use to establish the tunnel.

8. If necessary, repeat the previous substeps for any additional external devices you want to add for the same external connection (same VRF).

9. If necessary, repeat this step for any additional external connections (different VRFs).

   Note that there's a one-to-one relationship for tunnel endpoints between CSRs and external devices, so while you can create additional external connectivity using different VRFs, you cannot create additional connectivity to the same external devices.