Adding and Deleting Sites

Adding Cisco DCNM Sites

This section describes how to add a DCNM site using the Nexus Dashboard GUI and then enable that site to be managed by Multi-Site Orchestrator.

Before you begin

  • You must ensure that the site(s) you are adding are running Cisco DCNM, Release 11.5(1) or later.

Procedure

Step 1

Log in to the Nexus Dashboard GUI
Step 2

Add a new site.

  1. From the left navigation menu, select Sites.

  2. In the top right of the main pane, select Actions > Add Site.

Step 3

Provide site information.

  1. For Site Type, select DCNM.

  2. Provide the DCNM controller information.

    You need to provide the Host Name/IP Address of the in-band (eth2) interface, User Name, and Password. for the DCNM controller currently managing your DCNM fabrics.

  3. Click Select Sites to select the specific fabrics managed by the DCNM controller.

    The fabric selection window will open.
Step 4

Select the fabrics you want to add to the Nexus Dashboard.

  1. Check one or more fabrics that you want to be available to the applications running in your Nexus Dashboard.

  2. Click Select.

Step 5

In the Add Site window, click Add to finish adding the sites.

At this time, the sites will be available in the Nexus Dashboard, but you still need to enable them for Multi-Site Orchestrator management as described in the folowing steps.

Step 6

Repeat the previous steps for any additional DCNM controllers.
Step 7

From the Nexus Dashboard's Service Catalog, open the Multi-Site Orchestrator application.

You will be automatically logged in using the Nexus Dashboard user's credentials.
Step 8

In the Multi-Site Orchestrator GUI, enable the sites.

  1. From the left navigation menu, select Infrastructure > Sites.

  2. In the main pane, change the State from Unmanaged to Managed for each fabric that you want the MSO to manage.

    If the fabric you are managing is part of a DCNM Multi-Site Domain (MSD), it will have a Site ID already associated with it. In this case, simply changing the State to Managed will manage the fabric.

    However, if the fabric is not part of a DCNM MSD, you will also be prompted to provide a Fabric ID for the site when you change its state to Managed.

    Note 

    If you want to manage both kinds of fabrics, those that are part of an existing MSD and those that are not, you must on-board the MSD fabrics first, followed by any standalone fabrics.

Removing Sites

This section describes how to disable site management for one or more sites using the Multi-Site Orchestrator GUI. The sites will remain present in the Nexus Dashboard.

Before you begin

You must ensure that all templates associated with the site you want to remove are not deployed.

Procedure

Step 1

Open the Multi-Site Orchestrator GUI.

You can open the MSO application from the Nexus Dashboard's Service Catalog. You will be automatically logged in using the Nexus Dashboard user's credentials.

Step 2

In the Multi-Site Orchestrator GUI, disable the sites.

  1. From the left navigation menu, select Infrastructure > Sites.

  2. In the main pane, change the State from Managed to Unmanaged for each fabric that you want the MSO to stop managing.

    Note 

    If the site is associated with one or more deployed templates, you will not be able to change its state to Unmanaged until you undeploy those templates.

Cross Launch to Fabric Controllers

Multi-Site Orchestrator currently supports a number of configuration options for each type of fabrics. For many additional configuration options, you may need to log in directly into the fabric's controller.

You can cross launch into the specific site controller's GUI from the MSO's Infrastucture > Sites screen by selecting the actions (...) menu next to the site and clicking Open in user interface. Note that cross-launch works with out-of-band (OOB) management IP of the fabric.

If your Nexus Dashboard and the fabric are configured for remote user authentication, you will be logged in automatically into the fabric's controller using the same log in information as the Nexus Dashboard user.