Log in to the Cisco Nexus Dashboard Orchestrator GUI.

In the left navigation menu, select Configure > Site To Site Connectivity.

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

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

Click View Details to load site settings.

Provide the Inter-Site Connectivity information.

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

2. (Optional) Enable the CloudSec Encryption knob encryption for the site.

   CloudSec Encryption provides intersite traffic encryption. The "Infrastructure Management" chapter in the Cisco Multi-Site Configuration Guide covers this feature in detail.

3. Specify the Overlay Multicast TEP.

   This address is used for the intersite L2 BUM and L3 multicast traffic. This IP address is deployed on all spine switches that are part of the same fabric, regardless of whether it is a single pod or multipod fabric.

   This address should not be taken from the address space of the original fabric's Infra TEP pool or from the 0.x.x.x range.

4. Specify the BGP Autonomous System Number.

5. (Optional) Specify the BGP Password.

6. Provide the OSPF Area ID.

   The following settings are required if you are using OSPF protocol for underlay connectivity between the site and the IPN. If you plan to use BGP instead, you can skip this step. BGP underlay configuration is done at the port level, as described in Configuring Infra: Spine Switches.

7. Select the OSPF Area Type from the drop-down list.

   The following settings are required if you are using OSPF protocol for underlay connectivity between the site and the IPN. If you plan to use BGP instead, you can skip this step. BGP underlay configuration is done at the port level, as described in Configuring Infra: Spine Switches.

   The OSPF area type can be one of the following:

   • nssa

   • regular

8. Configure OSPF policies for the site.

   The following settings are required if you are using OSPF protocol for underlay connectivity between the site and the IPN. If you plan to use BGP instead, you can skip this step. BGP underlay configuration is done at the port level, as described in Configuring Infra: Spine Switches.

   You can either click an existing policy (for example, msc-ospf-policy-default ) to modify it or click +Add Policy to add a new OSPF policy. Then in the Add/Update Policy window, specify the following:

   • In the Policy Name field, enter the policy name.

   • In the Network Type field, choose either broadcast, point-to-point, or unspecified.

     The default is broadcast.

   • In the Priority field, enter the priority number.

     The default is 1.

   • In the Cost of Interface field, enter the cost of interface.

     The default is 0.

   • From the Interface Controls drop-down list, choose one of the following:

     • advertise-subnet

     • bfd

     • mtu-ignore

     • passive-participation

   • In the Hello Interval (Seconds) field, enter the hello interval in seconds.

     The default is 10.

   • In the Dead Interval (Seconds) field, enter the dead interval in seconds.

     The default is 40.

   • In the Retransmit Interval (Seconds) field, enter the retransmit interval in seconds.

     The default is 5.

   • In the Transmit Delay (Seconds) field, enter the transmit delay in seconds.

     The default is 1.

9. (Optional) From the External Routed Domain drop-down, select the domain that you want to use.

   Choose an external router domain that you have created in the Cisco APIC GUI. For more information, see the Cisco APIC Layer 3 Networking Configuration Guide specific to your APIC release.

10. (Optional) Enable SDA Connectivity for the site.

    If the site is connected to an SDA network, enable the SDA Connectivity knob and provide the External Routed Domain, VLAN Pool, and VRF Lite IP Pool Range information.

    If you enable SDA connectivity for the site, you need to configure extra settings as described in the SDA use case chapter of the Cisco Multi-Site Configuration Guide for ACI Fabrics.

11. (Optional) Enable SR-MPLS Connectivity for the site.

    If the site is connected through an MPLS network, enable the SR-MPLS Connectivity knob and provide the Segment Routing global block (SRGB) range.

    The Segment Routing Global Block (SRGB) is the range of label values that are reserved for Segment Routing (SR) in the Label Switching Database (LSD). These values are assigned as segment identifiers (SIDs) to SR-enabled nodes and have global significance throughout the domain.

    The default range is 16000-23999.

    If you enable MPLS connectivity for the site, you need to configure extra settings as described in the "Sites Connected through SR-MPLS" chapter of the Cisco Multi-Site Configuration Guide for ACI Fabrics.

Configure intersite connectivity between on-premises and cloud sites.

1. Click +Add IPN Device to specify an IPN device.

2. From the drop-down, select one of the IPN devices you defined previously.

   The IPN devices must be already defined in the General Settings > IPN Devices list, as described in Configuring Infra: General Settings

3. Configure intersite connectivity for cloud sites.

   Any previously configured connectivity from the cloud sites to this on-premises site will be displayed here, but any additional configuration must be done from the cloud site's side as described in Configuring Infra for Cisco Cloud Network Controller Sites.