Log in to the Cisco Multi-Site Orchestrator GUI.

In the Main menu, select Infrastructure > Infra Configuration.

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

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

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

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

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

Log in to the Cisco Multi-Site Orchestrator GUI.

In the Main menu, select Infrastructure > Infra Configuration.

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

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

Provide the Overlay Configuration.

1. In the right <Site> Settings pane, select the Overlay Configuration tab.

2. In the right <Site> Settings pane, 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.

Provide the Underlay Configuration.

1. In the right <Site> Settings pane, select the Underlay Configuration tab.

2. Click Add Connectivity.

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

4. 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.

5. (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.

6. 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.

7. 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.

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

   When you establish underlay connectivity from Site1 to Site2, the reverse connetivity 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.