Cisco Nexus Dashboard Orchestrator for ACI Lab v1

First Published: 2021-07-22

Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
© 2021 Cisco Systems, Inc. All rights reserved.
 CONTENTS

CHAPTER 1 About 1
This Demonstration 1
Requirements 1
This Solution 1

Terminology 2
Topology 3
Before You Present 4
Get Started 4

CHAPTER 2 Scenarios 7

(Optional) Bypass Creating Users and Day 0 Infrastructure Configuration 7

Create New Users 12
Create New Sites 16
Day-0 Infrastructure Configuration 21

Create an MSC Tenant 34

ACI Multi-Site Use Cases 36

Layer 3 only Communication across Sites (Intra-Tenant and Intra-VRF) 36

Layer 3 only Communication across Sites and VRFs (Shared Services) 56

IP Mobility across Sites (Stretched BD without BUM Flooding) 64
Import Tenant Configuration from a Site 68

CHAPTER 3 What’s Next? 75

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

iii
Contents

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

iv
 CHAPTER 1
About
• This Demonstration, on page 1
• This Solution , on page 1
• Terminology, on page 2
• Topology, on page 3
• Before You Present, on page 4
• Get Started, on page 4

This Demonstration
Limitations: The demonstration environment is a simulated environment and there is no actual data plane,
therefore the fabrics will not establish OSPF/BGP adjacencies. All configurations will be lost after a reboot
of the APIC simulators.

Requirements
The table below outlines the requirements for this preconfigured demonstration.

Required Optional
Laptop Cisco AnyConnect®

This Solution
As the newest advance in the Cisco ACI methods to interconnect networks, Cisco ACI Multi-Site is an
architectural approach for interconnecting and managing multiple sites, each serving as a single fabric and
availability zone. As shown in the diagram, the Multi-Site architecture has three main functional components:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

1
 About
Terminology

• Two or more ACI fabrics built with Nexus 9000 switches deployed as leaf and spine nodes.
• One APIC cluster domain in each fabric.
• Nexus Dashboard with installed Multi-Site Orchestrator Service, which is used to manage the different
fabrics and to define inter-site policies.

Multi-Site has the following benefits:

• Complementary with Cisco APIC, in Multi-Site each site is an availability zone (APIC cluster domain),
which can be configured to be a shared or isolated change-control zone.
• MP-BGP EVPN is used as the control plane between sites, with data-plane VXLAN encapsulation across
sites.
• The Multi-Site solution enables extending the policy domain end-to-end across fabrics. You can create
policies in the Multi-Site GUI and push them to all sites or selected sites. Alternatively, you can import
tenants and their policies from a single site and deploy them on other sites.
• Multi-Site enables a global view of site health.
• From the GUI of the Multi-Site Orchestrator, you can launch site APICs.
• Cross-site namespace normalization is performed by the connecting spine switches. This function requires
Cisco Nexus 9000 Series switches with EX on the end of the name, or newer.
• Disaster recovery scenarios offering IP mobility across sites is one of the typical Multi-Site use cases.

Terminology
As a complementary product with Cisco ACI, much of the Cisco ACI Multi-Site terminology is shared with
ACI and APIC (for example, they both use the terms fabric, tenant, contract, application profile, EPG, bridge

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

2
 About
Topology

domain, and L3Out). For definitions of ACI terminology, see Cisco Application Centric Infrastructure
Fundamentals.
Micro-services architecture: In its first implementation, the Cisco ACI Multi-Site Orchestrator (inter-site
policy manager) is represented by a service running on a Nexus Dashboard virtual appliance. Nexus Dashboard
appliance with MSO service does not need to be connected to the ACI leaf nodes, because it is only required
to establish IP connectivity between the VMs and the OOB IP addresses of the different APIC cluster nodes.
Namespace: Each fabric maintains separate data in its name space, including such objects as the TEP pools,
Class-IDs (EPG identifiers) and VNIDs (identifying the different Bridge Domains and the defined VRFs).
The site-connecting spine switches (EX or later) perform the necessary namespace translation (normalization)
between sites.
Schema: Profile including the site-configuration objects that will be pushed to sites.
Site: APIC cluster domain or single fabric, treated as an ACI region and availability zone. It can be located
in the same metro-area as other sites or spaced world-wide.
Stretched: Objects (tenants, VRFs, EPGs, bridge-domains, subnets, or contracts) are stretched when they are
deployed to multiple sites.
Template: Child of a schema, a template contains configuration-objects that are shared between sites or
site-specific.
Template Conformity: When templates are stretched across sites, their configuration details are shared and
standardized across sites. To maintain template conformity, it is recommended to only make changes in the
templates, using the Multi-Site GUI and not in a local site's APIC GUI.

Topology
This content includes preconfigured users and components to illustrate the scripted scenarios and features of
the solution. Most components are fully configurable with predefined administrative user accounts. You can
see the IP address and user account credentials to use to access a component by clicking the component icon
in the Topology menu of your active session and in the scenario steps that require their use.

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

3
 About
Before You Present

Before You Present

Cisco dCloud strongly recommends that you perform the tasks in this document before presenting in front of
a live audience. This will allow you to become familiar with the structure of the document and content.
dCloud recommends using the Chrome browser for all demos.

PREPARATION IS KEY TO A SUCCESSFUL PRESENTATION.

Get Started
Follow the steps to schedule a session of the content and configure your presentation environment.

Procedure

Step 1 Initiate your dCloud session. [Show Me How]

Note It may take up to 10 minutes for your session to become active.

Step 2 Connect to the workstation using one of the available connection methods:
• Cisco AnyConnect VPN [Show Me How] and the local RDP client on your laptop [Show Me How]
(Workstation 1: 198.18.133.36, Username: dCloud\demouser, Password: C1sco12345

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

4
About
Get Started

• Cisco dCloud Remote Desktop client [Show Me How].

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

5
 About
Get Started

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

6
 CHAPTER 2
Scenarios
• (Optional) Bypass Creating Users and Day 0 Infrastructure Configuration, on page 7
• Create New Users, on page 12
• Create New Sites, on page 16
• Day-0 Infrastructure Configuration , on page 21
• Create an MSC Tenant , on page 34
• ACI Multi-Site Use Cases, on page 36

(Optional) Bypass Creating Users and Day 0 Infrastructure

Configuration
Your presentation can bypass user creation and day 0 configuration. This scenario instructs you on the steps
you must take to successfully create the sites required for the demo.
If you do not want to bypass day0 configuration and want to perform the entire demo, skip this scenario and
begin with the Create New Users, on page 12 scenario.

Important Name the sites exactly as instructed or you will be unable to complete the demo successfully.

Procedure

Step 1 Sign in to the Cisco Nexus Dashboard using admin/C1sco12345 and then, close the splash screen.
Step 2 In the left panel, Click Sites and then, click Actions > Add Site.
Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

7
 Scenarios
(Optional) Bypass Creating Users and Day 0 Infrastructure Configuration

Step 3 In Site Type, leave the default ACI type.

Step 4 In the Site Name field, enter San Francisco.
Step 5 In the Host Name / IP Address field, enter apic1-a.dcloud.cisco.com.
Step 6 Scroll up the page and then, in the User Name field, enter admin (even if it appears prepopulated).
Step 7 In the Password field, enter C1sco12345 (even if it appears prepopulated).
Step 8 Leave the other fields blank.
Step 9 (Optional) Drop the pin to locate your site on the map.
Step 10 Click Add.
Example:

The San Francisco site is listed in the Sites list and the Connectivity Status is Up.
Now you must add a second site to the Cisco Nexus Dashboard.

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

8
Scenarios
(Optional) Bypass Creating Users and Day 0 Infrastructure Configuration

Step 11 Click Actions > Add Site.

Example:

Step 12 In Site Types, leave the default ACI type.

Step 13 In the Site Name field, enter New York.
Step 14 In the Host IP Name / IP Address field, enter apic1-b.dcloud.cisco.com.
Step 15 Scroll up the page and then, in the User Name field, enter admin (even if it appears prepopulated).
Step 16 In the Password field, enter C1sco12345 (even if it appears prepopulated).
Step 17 Leave the other fields blank.
Step 18 (Optional) Drop the pin to locate your site on the map.
Step 19 Click Add.
Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

9
 Scenarios
(Optional) Bypass Creating Users and Day 0 Infrastructure Configuration

Step 20 Wait until the software discovers the New York site and then verify that both sites show Up in the Connectivity
Status and that the configuration URLs are correct.
Note It takes about two minutes for the status to update.
The Health Score filed can be in different states, including Critical; it is not important at this stage.
Example:

After adding both sites to the Cisco Nexus Dashboard, you must move them into a managed state in the
Multi-Site Orchestrator.

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

10
Scenarios
(Optional) Bypass Creating Users and Day 0 Infrastructure Configuration

Step 21 After adding the sites, on the desktop, click the Fix my demo shortcut.

Step 22 In the dialog, choose option 3, Skip intersite infra configuration.

Terraform automatically restores the day 0 infrastructure configuration on MSO from a preconfigured backup.
The script also configures the ACI sites.
This process three to four minutes to run.

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

11
 Scenarios
Create New Users

Step 23 When the script completes, open MSO then, click Infrastructure > Infrastructure Configuration and then,
verify the site configuration.
You should see BGPs, OSPFs, IP addresses, and so on, as in the image.

What to do next
Continue with Create an MSC Tenant , on page 34.

Create New Users

Use the privileges of the admin user to create user profiles with different functions, and to add sites to the
Multi-Site Policy Manager. These additional users and sites are in subsequent scenarios. The user admin is
predefined for this lab.

Note In the context of this guide, the terms Multi-Site Policy Manager, Multi-Site Manager, Multi-Site Orchestrator,
and Multi-Site Controller (MSC) are used interchangeably.

Procedure

Step 1 First, create a new user: double-click the Nexus Dashboard icon on the workstation desktop.

Step 2 Sign in using (admin/C1sco12345) and then, close the splash screen.

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

12
Scenarios
Create New Users

Step 3 In the left-menu: click Administrative > Users.

Note If necessary, scroll to the bottom and close the blue screen at startup.

Step 4 Click Actions > Create Local User.

Example:

Step 5 Configure the user-specific account information as follows:

• Username: demouser
• Password: C1sco123456!
• First Name: Demo
• Last Name: User

Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

13
 Scenarios
Create New Users

Step 6 Scroll up the page.

Step 7 In the EMAIL ADDRESS field – enter [email protected]
Step 8 Scroll the page up to show the Roles panel.
Notice that the User Roles screen shows a set of predefined roles and privileges (Read or Write). The following
user roles are available in Cisco Nexus Dashboard.
Administrator
Allows access to all objects and configurations.
User Manager
Allows access to users and authentication configurations.
Dashboard User
Allows access only to the Dashboard view and launching applications. It does not allow any changes to the
Cisco Nexus Dashboard configurations.
Site Administrator
Allows access to configurations related to the sites on-boarding and configuration.
Site Manager
Allows the application user to manage the sites used by that application.
Policy Manager
Allows the application user to view policy objects.
Tenant Manager
Allows the application user to view tenants.

Step 9 Check the Write Privilege check boxes for the Site Administrator, Site Manager, and Tenant Manager
roles and then, click Create.
Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

14
Scenarios
Create New Users

Step 10 Click and then, click Log Out.

Example:

Step 11 Sign in again using (demouser/C1sco123456!).

Step 12 Close the Splash Screen.

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

15
 Scenarios
Create New Sites

Step 13 Verify that the only options in the left-menu are Dashboard and Sites.
Example:

Step 14 Click and then, click Log Out.

Now you must connect the ACI Multi-Site Orchestrator to two different APIC domains, in New York and
San Francisco, and to be able to start centrally managing those different fabrics.

Create New Sites

In this scenario, you create new sites and set them up for management by Multi-Site Orchestrator.

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

16
Scenarios
Create New Sites

Procedure

Step 1 Sign in to the Cisco Nexus Dashboard using admin/C1sco12345 and then, close the splash screen.
Step 2 In the left panel, Click Sites and then, click Actions > Add Site.
Example:

Step 3 In Site Type, leave the default ACI type.

Step 4 In the Site Name field, enter San Francisco.
Step 5 In the Host Name / IP Address field, enter apic1-a.dcloud.cisco.com.
Step 6 Scroll up the page and then, in the User Name field, enter admin (even if it appears prepopulated).
Step 7 In the Password field, enter C1sco12345 (even if it appears prepopulated).
Step 8 Leave the other fields blank.
Step 9 (Optional) Drop the pin to locate your site on the map.
Step 10 Click Add.
Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

17
 Scenarios
Create New Sites

The San Francisco site is listed in the Sites list and the Connectivity Status is Up.
Now you must add a second site to the Cisco Nexus Dashboard.

Step 11 Click Actions > Add Site.

Example:

Step 12 In Site Types, leave the default ACI type.

Step 13 In the Site Name field, enter New York.
Step 14 In the Host IP Name / IP Address field, enter apic1-b.dcloud.cisco.com.
Step 15 Scroll up the page and then, in the User Name field, enter admin (even if it appears prepopulated).
Step 16 In the Password field, enter C1sco12345 (even if it appears prepopulated).
Step 17 Leave the other fields blank.

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

18
Scenarios
Create New Sites

Step 18 (Optional) Drop the pin to locate your site on the map.
Step 19 Click Add.
Example:

Step 20 Wait until the software discovers the New York site and then verify that both sites show Up in the Connectivity
Status and that the configuration URLs are correct.
Note It takes about two minutes for the status to update.
The Health Score filed can be in different states, including Critical; it is not important at this stage.
Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

19
 Scenarios
Create New Sites

After adding both sites to the Cisco Nexus Dashboard, you must move them into a managed state in the
Multi-Site Orchestrator.

Step 21 In the menu, click Services > Multi-Site Orchestrator.

Example:

Multi-Site Orchestrator opens in a new tab.

Step 22 In Multi-Site Orchestrator, in the menu, click Infrastructure > Sites.
Example:
Notice that the sites are unmanaged.

Move each fabric that is connected to the MSO to Managed state and assign a unique Site-ID value. If you
configure overlapping site IDs to separate fabrics, MSO issues a warning.
Step 23 Expand the State drop-down list for San Francisco then, click Managed then, in the Site ID field, enter 1
and then, click Add.
Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

20
 Scenarios
Day-0 Infrastructure Configuration

a) Wait for successful notification about the state change.

Step 24 Expand the State drop-down list for New York then, click Managed then, in the Site ID field, enter 2 and
then, click Add.
Step 25 Verify that both sites are in Managed state now.
MSO discovers all APIC controllers in the cluster automatically. The URL column displays the IP address
of one of the APICs.

Day-0 Infrastructure Configuration

Perform the Day-0 configuration for interconnecting ACI fabrics (sites), which is managed from the Multi-Site
manager. The following configuration tasks are managed from the MSC.
• Spine interface configuration (Interface selection, IP address assignment, MTU setting)
• Control Plane E-TEP configuration (Used for BGP EVPN peering between sites)
• Unicast Data plane E-TEP configuration
• Multicast Data plane E-TEP configuration
• OSPF area configuration for spine to IP network connections (area id, area type)
• BGP Autonomous System Number assignment (uses fabric ASN)

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

21
 Scenarios
Day-0 Infrastructure Configuration

• BGP community configuration

• External L3 domain selection
• The following configuration tasks are managed from the APIC at each site (site local configuration).

The following configuration tasks are managed from the APIC at each site (site local configuration).
• Configuration of the access policies for the External L3 domain (Spine switch profile, interface profile,
interface policy group, attachable entity profile, external L3 domain)
• BGP Route Reflector Policy

The MSC will read in the BGP ASN and External L3 Domains from each site. Add these to each site from
the respective APICs.
Now you will enter an Autonomous System Number and an External Routed Domain for the San Francisco
site (Site 1). These elements are required for BGP routing.

Procedure

Step 1 Double-click

on the workstation desktop and log in (admin/C1sco12345).

Step 2 In the Welcome to APIC banner, check Do not show on login and then, click Begin first time setup.
Note Ignore any warnings to update the license for APIC. Also, if for some reason, the First time Set
Up banner does not appear automatically, click System > QuickStart > First time setup of the
ACI fabric to start the set up.

Example:

Step 3 Click Begin under BGP setting.

Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

22
Scenarios
Day-0 Infrastructure Configuration

Step 4 Enter 65001 in the Autonomous System Number field, select spine 104 and 103 and click Save and
Continue.
Example:

Step 5 Click Close (at the bottom).

Note Even though there are additional configuration sections marked as mandatory (DNS, NTP, Intersight
Proxy), they are no relevant to this demo and you can leave them unconfigured.

Step 6 Click Fabric > Access Policies in the top menu and expand Physical and External Domains.
Step 7 Click L3 Domains.
Step 8 Expand the Tools menu at the upper right and select Create L3 Domain.
Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

23
 Scenarios
Day-0 Infrastructure Configuration

Step 9 Enter Multisite_External_L3_Domain in the Name field and click Submit.

Example:

Step 10 Double-click

on the workstation desktop and log in to Site 2 (admin/C1sco12345).

Step 11 In the Welcome to APIC banner, check Do not show on login and then, click Begin first time setup.
Step 12 Click Begin under BGP setting.
Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

24
Scenarios
Day-0 Infrastructure Configuration

Step 13 Enter 65002 in the Autonomous System Number field, select spine 104 and 103 and click Save and
Continue.
Example:

Step 14 Click Close (at the bottom).

Note Even though there are additional configuration sections marked as mandatory (DNS, NTP, Intersight
Proxy), they are no relevant to this demo and you can leave them unconfigured.

Step 15 Click Fabric > Access Policies in the top menu and expand Physical and External Domains.
Step 16 Click L3 Domains.
Step 17 Expand the Tools menu and select Create L3 Domain.

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

25
 Scenarios
Day-0 Infrastructure Configuration

Example:

Step 18 Enter Multisite_External_L3_Domain in the Name field and click Submit.

Example:

Now you will use MSO to configure Infra for San Francisco (Site 1) and New York (Site 2). Perform the same
procedure for each site, noting the difference in IP addresses and other values.

Step 19 Return and log in (admin/Cisco12345) to the Nexus Dashboard then, in the menu, click Services and
open the Multi-Site Orchestrator.
Example:

Step 20 Click Infrastructure > Infra Configuration to display the BGP and OSPF settings page and then, click
Configure Infra.
Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

26
Scenarios
Day-0 Infrastructure Configuration

Note The default setting for BGP is full mesh and uses standard BGP timer values. The default OSPF
network type is point-to-point.

The Fabric Connectivity Infra screen displays.

Step 21 Select San Francisco in the side menu to add Infra settings for Site 1.
Note If configuring Site 2, select New York.

Step 22 Highlight Spine 1 and click + Add Port.

Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

27
 Scenarios
Day-0 Infrastructure Configuration

Step 23 Enter 5/32 in the Port ID field for Spine 1.

Note These settings are the same for San Francisco and New York.

Step 24 Enter the Spine 1 interface address in the IP Address field.

a) Site 1 (San Francisco): 10.1.0.1/31
b) Site 2 (New York): 10.2.0.1/31
Step 25 Leave the default MTU (9216), default OSPF policy, and OSPF authentication and then, click Save.
Example:

Step 26 Toggle the button to enable BGP Peering.

Step 27 Enter the appropriate IP address in the BGP-EVPN ROUTER_ID field for Spine 1.

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

28
Scenarios
Day-0 Infrastructure Configuration

• Site 1: 10.1.100.1
• Site 2: 10.2.100.1

Note Inter-site control plane: Endpoint reachability information is exchanged across sites using a
Multiprotocol-BGP (MP-BGP) Ethernet VPN (EVPN) control plane. This approach allows the
exchange of MAC and IP address information for the endpoints that communicate across sites.
MP-BGP EVPN sessions are established between the spine nodes deployed in separate fabrics.

Example:

Step 28 Select Spine 2 and click Add Port.

Step 29 Enter 5/32 in the Port ID field for Spine 2.
Note These settings are the same for San Francisco and New York.

Step 30 Enter the Spine 2 interface address in the IP Address field.

• Site 1: 10.1.0.3/31
• Site 2: 10.2.0.3/31

Step 31 Leave the default MTU (9216), default OSPF policy, and OSPF authentication and then, click Save.
Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

29
 Scenarios
Day-0 Infrastructure Configuration

Step 32 Toggle the button to enable BGP Peering.

Step 33 Enter the appropriate IP address in the BGP-EVPN ROUTER_ID field for Spine 2.
• Site 1: 10.1.100.2
• Site 2: 10.2.100.2

Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

30
Scenarios
Day-0 Infrastructure Configuration

Step 34 Configure Unicast Data Plane ETEP for Site 1 as follows:

Step 35 Select pod-1.
Step 36 Enter the appropriate IP address in the OVERLAY UNICAST TEP field.
• San Francisco: 10.1.100.100
• New York: 10.2.100.100

Example:

Step 37 Select the site box (San Francisco or New York) to bring up the pane to enable Multi-Site.
Step 38 Configure the following fields as shown:
• ACI Mult-Site: On
• OVERLAY MULTICAST TEP: SF: 10.1.100.200 / NY: 10.2.100.200
• BGP Autonomous System Number: SF: 65001 / NY: 65002
• OSPF Area ID: 0
• OSPF Area Type: regular

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

31
 Scenarios
Day-0 Infrastructure Configuration

• External Routed Domain: Multisite_External_L3_Domain

Example:

Note The External Routed Domain drop down will display the domain previously configured on the APIC
(Multisite_External_L3_domain).

Step 39 Click Deploy to push the Infra L3out configuration to the APIC.
Step 40 Wait for the success message and close the Fabric Connectivity Intra window.
Step 41 Add the Multipod Data Plane TEP configuration as follows.
a) In the APIC window for the site being configured, click Tenants > infra > Policies > Protocol > Fabric
Ext Connections Policies and click Fabric Ext Connection Policy.
b) Enter extended:as2-nn4:5:16 in the Community field.
c) In the work pane, double-click Pod ID 1.
Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

32
Scenarios
Day-0 Infrastructure Configuration

Step 42 Click + to add a subnet.

Step 43 Enter the MultiPod Dataplane TEP in the Subnet field.
• San Francisco: 10.1.200.200/32
• New York: 10.2.200.200/32

Step 44 Click Update, and then click Close.

Step 45 Click Submit and, and then click Submit Changes in the pop-up window to confirm the changes.
Example:

Step 46 Click Tenant > infra > Networking > L3Outs and verify that an L3outs called intersite has been configured
under the infra tenant. This indicates that Infra L3out has been successfully configured on APIC for Site 1.
Note The object for the L3Out also includes a small cloud icon. All ACI objects configured by the MSC
will include this icon.

Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

33
 Scenarios
Create an MSC Tenant

Step 47 Repeat all the steps for the New York site, using the New York values indicated in the text.

Create an MSC Tenant

Create a tenant in the Multi-Site Orchestrator that will be deployed across both sites. This will be a greenfield
tenant that does not currently exist at any sites, and the configuration will be pushed to both sites at the same
time.

Procedure

Step 1 In the Multi-Site Orchestrator, select Application Management > Tenants in the side menu and click Add
Tenant.
Example:

Step 2 Enter Tesla in the Display Name field.

Step 3 Select both San Francisco and New York and click Save to push the Tenant configuration to APIC.
Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

34
Scenarios
Create an MSC Tenant

Step 4 Return to the APIC SF and APIC NY windows. Click Tenants > ALL TENANTS in each window and
verify that the Tesla tenant has been created on both fabrics.
Example:

Step 5 In either APIC SF or APIC NY, double-click Tesla to proceed to the APIC window for Tesla.

Note that the tenant object includes the cloud symbol, indicating that this object has been configured from
the MSC. The APIC GUI will also display a message to this effect.
Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

35
 Scenarios
ACI Multi-Site Use Cases

ACI Multi-Site Use Cases

This scenario contains four common Multi-Site use cases.

Layer 3 only Communication across Sites (Intra-Tenant and Intra-VRF)

This use case will show Layer-3 communication across sites. The Tenant and VRF objects will be stretched
across sites, but the BD, Subnet, and EPG configuration will be local to each site.

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

36
Scenarios
Layer 3 only Communication across Sites (Intra-Tenant and Intra-VRF)

Procedure

Step 1 In the Multi-Site Configuration window, select Application Management > Schemas from the vertical
menu and then, click Add Schema.
Example:

Step 2 Enter L3-stretch-schema as the schema name and then, click Add.
Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

37
 Scenarios
Layer 3 only Communication across Sites (Intra-Tenant and Intra-VRF)

Note Schemas contain templates. The templates are associated to one or more sites and are used to define
the objects that will be stretched between sites or will remain site-local.

Step 3 Click + to add the Template then, in the Select a Template type dialog, select ACI Multi-cloud and then,
click Add.
Example:

Step 4 Because this configuration will stretch the Tenant and VRF, click Template 1, then click the pencil icon and
then, name the template SF and NY Template.
Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

38
Scenarios
Layer 3 only Communication across Sites (Intra-Tenant and Intra-VRF)

Also, you can change the template name by clicking Template Settings > Display Name.
Step 5 In Template Settings, in the Select a Tenant drop-down, select Tesla.
Example:

Step 6 Under VRFs, click Add VRF.

For this use case the only stretched object (commonly defined across sites) will be the VRF.
Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

39
 Scenarios
Layer 3 only Communication across Sites (Intra-Tenant and Intra-VRF)

Step 7 In the Display Name field, enter VRF1.

Example:

Because the objects in this template will be stretched across both sites, it must be associated with both sites.

Step 8 Next to Sites in the side menu, select +.

Step 9 Select both San Francisco and New York and then, click Save.
Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

40
Scenarios
Layer 3 only Communication across Sites (Intra-Tenant and Intra-VRF)

Note When configuration is added to the MSO there is a Save button and a Deploy to sites button. Saving
the template configuration saves it to the MSO database but does not make any changes to the
APICs. Only after selecting Deploy to sites is the configuration change pushed to the APICs. At
this point in the configuration, we have added a template and created a VRF but have not saved nor
deployed the configuration

Step 10 Click Save to save the configuration to the MSO without deploying to APIC.
Example:

Step 11 Click Deploy to sites.

A window appears showing which changes will be deployed and to which sites.
Step 12 Click Deploy, which will result in the creation of the VRF in both sites.
Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

41
 Scenarios
Layer 3 only Communication across Sites (Intra-Tenant and Intra-VRF)

Step 13 Wait for the successful deployment message.

Now you will add an SF Only Template and associate it to the Tesla tenant. This template will contain the
BD, Subnets, and EPGs that will be locally deployed at site 1.

Step 14 In the Multi-Site Configuration window, select the + next to Templates then, in Template type select ACI
Multi-cloud and then, click Add.
Step 15 Click on Template2, then click the pencil icon so you can rename it.
Step 16 Enter SF Only in the Name field.
Step 17 In Tenant Settings, in the Select a Tenant drop-down, select Tesla to associate the tenant.
Example:

Step 18 Next to Application Profile, select Add Application Profile.

Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

42
Scenarios
Layer 3 only Communication across Sites (Intra-Tenant and Intra-VRF)

Step 19 In the Display Name field, enter Webapp.

Example:

Step 20 Click Add EPG and then, enter Web in the Display Name field.
Example:

Step 21 Select the drop-down for the Bridge Domain to associate the Web EPG to a bridge domain.
Step 22 Enter Web-BD in the Bridge Domain field. Because Web-BD does not currently exist, the option to create
the object is one of the choices on the drop-down, click "Web-BD" was not found. Click to create
"Web-BD".
Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

43
 Scenarios
Layer 3 only Communication across Sites (Intra-Tenant and Intra-VRF)

Step 23 Scroll down and select the Web-BD under Bridge Domain.
The default BD settings will appear on the right-side pane. This BD will not be stretched across sites.
a) Uncheck the L2 STRETCH box.
Step 24 Acknowledge the Warning by clicking Yes.
Note When the L2STRETCH box is unchecked the option to add a BD subnet is removed. This is because
the BD becomes a site local configuration. The site local configuration will be covered in a few
more steps

Step 25 On the Virtual Routing and Forwarding drop-down, select VRF1 (the VRF created in the SF and NY
Template).
Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

44
Scenarios
Layer 3 only Communication across Sites (Intra-Tenant and Intra-VRF)

Step 26 Select + next to Sites, use the drop-down to add the SF Only template to San Francisco.
This associates the template to only San Francisco Site.

Step 27 Click Save to close the Add Sites window.

Example:

Step 28 At the top of the screen, click Save.

Note You can save and deploy to sites in one step by just selecting deploy to sites. The configuration will
be saved to the MSO.

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

45
 Scenarios
Layer 3 only Communication across Sites (Intra-Tenant and Intra-VRF)

Step 29 Highlight the SF Only Template and Click Deploy To Sites.

Example:

Step 30 Click Deploy.

The MSO shows that the changes are only being pushed to San Francisco.

Step 31 Wait for the Successfully deployed message.

Note Site-local configuration changes are not displayed in the Template view. They are visible only in
the site view.

Step 32 Select San Francisco SF Only in the vertical menu to view the site-local changes.
Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

46
Scenarios
Layer 3 only Communication across Sites (Intra-Tenant and Intra-VRF)

Step 33 Select Web-BD and then, click + Add Subnet to add a subnet.
Example:

Step 34 Add 10.1.1.254/24 in the Gateway IP field and then, click Save.
Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

47
 Scenarios
Layer 3 only Communication across Sites (Intra-Tenant and Intra-VRF)

Step 35 At the top, click Save and select SF Only Template then click Deploy to Sites to deploy the changes to the
site, then click Deploy.
Example:

Note EPGs are also associated to domains (physical or VMM domains). The domain association and
static path binding configuration is also done from the MSO. This will always be a site local
configuration task and will be configured from selecting the site just as what was done for the BD
subnet. In this lab we will not be configuring the domain but be aware that this configuration is
always site local.

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

48
Scenarios
Layer 3 only Communication across Sites (Intra-Tenant and Intra-VRF)

Step 36 Repeat the previous section to create a NY Only template and associate it to the Tesla tenant with the following
changes:
a) Create a NY Only template
• Application Profile Name: Webapp
• EPG Name: App
• Bridge Domain Name: App-BD

b) Bridge Domain Name: App-BD

c) Add the NY Only template to Site 2 (New York).
d) Add the BD subnet for App-BD.
Remember to select the NY Site on the left pane for site local configuration.
Gateway IP: 10.1.2.254/24
At this point, both sites have been configured with a tenant called Tesla and an application profile called
Webapp. A Web EPG and BD has been configured in San Francisco and an App EPG and BD has been
configured in New York. There is no communication at this time between sites, and the Web BD subnet
in San Francisco is not known to New York and vice versa for the App BD in New York. A contract is
required in order to allow communication between sites and to advertise endpoint IP address information
between sites. Since this contract will be used by both EPGs we will configure it under the SF and NY
Template.

Step 37 Select SF and NY Template in the vertical menu.

Step 38 In Contracts, click Add Contract.
Step 39 Enter web-to-app in the Display Name field.
Example:

Step 40 Scroll down to Filters then, click Add Filter and then, in the Display Name field, enter any.
Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

49
 Scenarios
Layer 3 only Communication across Sites (Intra-Tenant and Intra-VRF)

Step 41 Click + Add Entry to add an entry for the filter.

Step 42 In the Name field, enter any and then, click Save.
Example:

Step 43 Scroll up and click the web-to-app contract.

Step 44 Click + Add Filter to add a filter.

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

50
Scenarios
Layer 3 only Communication across Sites (Intra-Tenant and Intra-VRF)

Example:

Step 45 In the Name drop-down, select any.

Step 46 In the Directive field, select none to configure the Filter Chain.
Example:

Step 47 Click Save, and then Deploy to Sites.

Step 48 Click Deploy to deploy the contract to both San Francisco and New York sites.
Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

51
 Scenarios
Layer 3 only Communication across Sites (Intra-Tenant and Intra-VRF)

Now you will add a web-to-app provider contract to the Web EPG in the SF Only template, and a web-to-app
consumer contract to the App EPG in the NY Only template. This will enable the application tiers to
communicate between sites as long as they are deployed in the same tenant.

Step 49 In the vertical menu, select SF Only.

Step 50 Click Web EPG.
Step 51 Click + Add Contract to add a contract to the EPG.
Example:

Step 52 In the Contract drop-down, select web-to-app.

Step 53 In the Type drop-down, select provider and then, click Save.
Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

52
Scenarios
Layer 3 only Communication across Sites (Intra-Tenant and Intra-VRF)

Step 54 In the vertical menu, select NY Only.

Step 55 Click the App EPG.
Step 56 Click + Add Contract to add a contract to the EPG.
Example:

Step 57 In the Contract drop-down, select web-to-app.

Step 58 In the Type drop-down, select consumer and then, click Save.
Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

53
 Scenarios
Layer 3 only Communication across Sites (Intra-Tenant and Intra-VRF)

Step 59 Click Save.

Step 60 Click Deploy to Sites on the main page.
Step 61 Click Deploy to deploy the NY Only template to the New York site.
Step 62 Click SF Only in the vertical menu.
Step 63 Click Deploy to sites.
Step 64 Click Deploy to deploy the SF Only template to the San Francisco site.
When the contract is applied to the Web and App EPGs the Web EPG and BD are pushed to the NY site and
the App EPG and BD are pushed to the SF site, you will verify the configuration in the APIC.

Step 65 Open either APIC NY or APIC SF if they are not already open.
Step 66 Click Tenants and double-click Tesla.
Step 67 Expand Tenant Tesla > Application Profiles > Webapp > Application EPGs and verify the presence of
the Web (SF APIC) and App (NY APIC) EPGs.
Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

54
Scenarios
Layer 3 only Communication across Sites (Intra-Tenant and Intra-VRF)

Step 68 Click Tenant > Tesla > Networking > Bridge Domains and verify the presence of the Web-BD (SF
APIC) and App-BD (NY APIC) bridge domains.
Example:

Step 69 Click Application Profiles > Webapp application profile.

Step 70 Click the Topology tab and show the presence of the contract that allows the EPGs to communicate.
Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

55
 Scenarios
Layer 3 only Communication across Sites and VRFs (Shared Services)

Layer 3 only Communication across Sites and VRFs (Shared Services)

This use case is similar to the one completed to enable L3 communication across sites. The difference is this
use case provides shared services access to resources that are deployed in a site as part of a dedicated Shared
VRF/BD/EPG object, as shown in the following figure.

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

56
Scenarios
Layer 3 only Communication across Sites and VRFs (Shared Services)

Procedure

Step 1 In the Multi-Site Orchestrator window, select Schemas > L3 stretch schema and then, select the SF Only
template.
Step 2 To create a new VRF, in the VRFs section, click Add VRF and then, in the Display Name field, enter VRF2.
Example:

Step 3 In the Bridge Domains section, click Web-BD and then, under Virtual Routing & Forwarding, select
VRF2.
Example:

Step 4 To create a new VRF, select the NY Only template then, under VRF, in the Display Name field, enter Shared
VRF.
Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

57
 Scenarios
Layer 3 only Communication across Sites and VRFs (Shared Services)

Step 5 To create a new Bridge Domain, in the Bridge Domain field, click + Add Bridge Domain and enter the
following attributes.
• Display Name: Shared-BD
• Virtual Routing & Forwarding: Shared VRF

Example:

Step 6 Scroll down the page then, select + Add Subnet then, in the Add Subnet dialog, enter the following attributes
and then, click Save.
• Gateway IP: 10.10.1.254/24
• Shared between VRFS: checked

Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

58
Scenarios
Layer 3 only Communication across Sites and VRFs (Shared Services)

Step 7 To create a new EPG, scroll up to the Application Profile section, click + Add EPG and then, enter the
following properties.
• Display Name: DNS
• Bridge Domain: Shared-BD

Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

59
 Scenarios
Layer 3 only Communication across Sites and VRFs (Shared Services)

Important Because the EPG provides services to other EPGs, you must remember to add the IP subnet
information under the EPG at the site level.

Step 8 To create a new subnet, in the DNS EPG work pane, click + Add Subnet then, in the Add Subnet dialog,
enter the following attributes and then, click Save.
• Gateway IP: 10.10.1.254/24
• Shared between VRFs: checked
• No Default SVI Gateway: checked

Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

60
Scenarios
Layer 3 only Communication across Sites and VRFs (Shared Services)

Note The sole purpose of defining the IP subnet information under the provider EPG is to enable the
necessary VRF rout-leaking functions between the Shared VRF and the other VRFs accessing the
shared services. The IP subnet that is configured at the BD provides the default gateway services,
so it is important to select the No Default SVI Gateway flag.

Step 9 To create the web-to-dns contract and ensure that the DNS EPG provides it, in the menu, under Templates,
select NY Only then, in the Contracts field, click Add Contract and then, enter the following attributes.
• Display Name: web-to-dns
• Scope: tenant
• Filter Chain: click + Add Filter and then, select any

Note By default, the contracts are created with VRF scope. In this case, the Web EPG, which is part of
a different VRF consumes toe contract so you must modify the scope of the contract to be either
tenant or global.
Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

61
 Scenarios
Layer 3 only Communication across Sites and VRFs (Shared Services)

Step 10 Under EPG, click DNS and then, click + Add Contract.
Example:

Step 11 In the Add Contract dialog, in the Contract field, select web-to-dns then, in the Type field, select provider
and then, click Save.
Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

62
Scenarios
Layer 3 only Communication across Sites and VRFs (Shared Services)

Step 12 To push the configuration to New York, click Deploy to Sites and then, click Deploy.
Now configure the Web EPG to consume the web-to-dns contract.

Step 13 In the menu, under Templates, click SF Only then, under EPG, click Web and under contracts, click + Add
Contract.
Example:

Step 14 In the Add Contract dialog, in the Contract field, select web-to-dns then, in the Type field, select consumer
and then, click Save.
Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

63
 Scenarios
IP Mobility across Sites (Stretched BD without BUM Flooding)

Step 15 To push out the new configuration, click Deploy to Sites and then, click Deploy.
Step 16 Verify the configuration that is deployed to San Francisco (apic1-a).
a) Log into the APIC and then click Tenants > Tesla > Application Profiles > Webapp.
b) Click Topology.
Example:

IP Mobility across Sites (Stretched BD without BUM Flooding)

In this use case, the requirement is to have IP mobility across sites (same BD and subnet) but without enabling
BUM flooding.
This use case is typical for disaster recovery sites where there is not a requirement for mobility (vMotion)
across sites but allows the application to be brought up at a DR site without having to re-IP the application
servers.
The suppression of BUM flooding across sites provides more resiliency across sites since a problem (like a
broadcast storm) hitting site 1 won’t be able to propagate to the other sites.

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

64
Scenarios
IP Mobility across Sites (Stretched BD without BUM Flooding)

A new BD, called DB-BD, will exist on both the San Francisco and New York sites, and will enable this use
case on the Tesla tenant.

Procedure

Step 1 In ACI MSO, click Schemas > L3-stretch-schema > SF and NY Template.
Step 2 In the Bridge Domain field select Add Bridge Domain, and configure with the following:
• Display Name: DB-BD
• Virtual Routing & Forwarding: VRF1
• INTERSITE BUM TRAFFIC ALLOW: Deselected (Click Yes on the Warning dialog)
• Add Subnet: 10.3.1.254/24

Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

65
 Scenarios
IP Mobility across Sites (Stretched BD without BUM Flooding)

Note At this point, there are no EPGs that are shared across sites, so the Webapp Application profile has
not been configured under the SF and NY template.

Step 3 Click Save.

Step 4 Ensure the SF and NY Template is selected.
a) Click Add Application Profile and then, in the Display Name, enter Webapp.
(The Application Profile name is case-sensitive, so be consistent with the name used previously).

Step 5 Click +Add EPG to create a new EPG with the following configuration:
• Display Name: DB
• Bridge Domain: DB-BD

Step 6 Click Save and Deploy to Sites.

Step 7 Click Deploy to push out the configuration.
Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

66
Scenarios
IP Mobility across Sites (Stretched BD without BUM Flooding)

Step 8 Verify the configuration has been deployed to San Francisco (apic1-a).
a) Log into the APIC and click Tenants > Tesla > Application Profiles > Webapp.
Step 9 Select the Topology tab.
Example:

Step 10 Verify the configuration has been deployed to New York (apic1-b).
a) Log into the APIC and click Tenants > Tesla > Application Profiles > Webapp.
Step 11 Select the Topology tab.
Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

67
 Scenarios
Import Tenant Configuration from a Site

Import Tenant Configuration from a Site

This is an important use case, because it will be deployed in migration scenarios where ACI has already been
deployed in a fabric and now there is a requirement to connect the existing fabric to a new greenfield ACI
environment using Multi-Site Orchestrator. This implies that the ACI Multi-Site Policy Manager will be
inserted in the deployment and both sites will be added to it.
Use this procedure to import the existing configuration for a tenant from a brownfield ACI fabric, and stretch
the objects associated to that tenant (application profile with corresponding EPGs, BDs and VRFs) toward
one (or more) greenfield ACI fabrics. In the context of this lab, the brownfield site is San Francisco, and the
new greenfield fabric is New York.

Procedure

Step 1 In the APIC for the San Francisco (apic1-a) screen, click Tenants > Brownfield.
Step 2 Click Tenant Brownfield from the menu.
Note that this tenant has the following configuration:
• VRF: Brownfield-VRF
• Bridge Domain: Brownfield-BD
• Application Profile: AP
• Application EPG: Brownfield-EPG

Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

68
Scenarios
Import Tenant Configuration from a Site

Step 3 Return to ACI Multisite Orchestrator Home page and then, click Application Management > Tenants >
Add Tenant.
Step 4 Enter the Display Name Brownfield and select both San Francisco and New York as the associated
sites
Step 5 Click Save.
Note It is essential that the name of the tenant created on MSC matches the name of the tenant in the
brownfield fabric from where the configuration should be imported. The newly created tenant should
then be associated to both existing sites since the configuration will be imported from one and
stretched toward the other.

Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

69
 Scenarios
Import Tenant Configuration from a Site

Step 6 Click Application Management > Schemas > Add Schema.

Step 7 Create a new schema called Migration-Schema.
This new schema will be used to perform the import of the configuration from ‘San Francisco’ into a new
‘Migration-Template’.

Step 8 Click + next to Templates to build your schema and then, select the default type ACI Multi-cloud.
Example:

Step 9 Click here to select a tenant and then, select the Brownfield tenant.
Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

70
Scenarios
Import Tenant Configuration from a Site

Step 10 Click Save to save the schema.

The Import button appears under Template.
Step 11 Click Import and select San Francisco to import the Brownfield tenant configuration into the Multi-Site
manager.
Example:

Step 12 In the resulting window, select the Application Profile and select AP.
The Import Relations toggle automatically switches to ON to import all the objects associated to the
Brownfield-AP application profile.
Step 13 Click Import and then, click Save.
Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

71
 Scenarios
Import Tenant Configuration from a Site

Step 14 Select the Brownfield-BD bridge domain to verify that the configuration is not stretched (which is expected,
since it was imported from a specific site).
Step 15 Click the L2 Stretch check box to allow to stretch it to the Greenfield site. Click Yes to acknowledge the
warning.
Step 16 Check the Intersite BUM Traffic Allow box to ensure that BUM traffic is allowed.
Note This step is required in a real-life scenario to enable the migration of workloads from Brownfield
to Greenfield, leveraging live migration technologies (for example, vMotion in a vSphere
environment).

Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

72
Scenarios
Import Tenant Configuration from a Site

Now that the configuration has been imported to the Multi-Site Orchestrator, it is required to push the objects
toward the Greenfield ACI fabric (New York site).
Step 17 Rename the Template1 to Migration-Template.
Step 18 Now, associate the Migration-Template to the New York site.
a) Under Sites, click +, select New York, and then click Save.
Example:

Step 19 On the top menu, click Save again.

Step 20 Click Deploy to Sites to push the configuration to the Greenfield site.
Step 21 Click Deploy again.
This will push the objects imported from the brownfield site toward the Greenfield ACI fabric.
Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

73
 Scenarios
Import Tenant Configuration from a Site

Step 22 Verify that the configuration is now displayed correctly in the New York APIC controller (apic1-b).
Example:

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

74
 CHAPTER 3
What’s Next?
Check out the related information.
• Cisco Nexus Dashboard Insights for ACI v1
• Cisco ACI 5.1 with VMware Lab v1
• Multi-site Configuration for DCNM Managed Fabrics using MSO on Nexus Dashboard v1

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

75
 What’s Next?

Cisco Nexus Dashboard Orchestrator for ACI Lab v1

76