Cisco Cloud Control Getting Started

 
Updated October 27, 2026
PDF
Is this helpful? Feedback

Cisco Cloud Control

Cisco Cloud Control is the unified operations platform for AgenticOps. It brings every Cisco domain into one consistent environment, enabling teams to proactively manage, govern, and operate across the full IT estate from a single experience. The platform simplifies management by offering a single operational interface that complements existing Cisco product controllers, reducing complexity and improving efficiency for IT operations. It enables seamless cross-domain workflows and a consistent user experience without replacing individual product dashboards.

By bringing together inventory, topology, actions, identity, and workflows, Cisco Cloud Control gives operators the context and tools to understand their environment, investigate issues across domains, and take action within one operating experience. AI Assistant provides a natural-language entry point for asking questions, understanding the environment, and starting an investigation. When an issue requires more context or a coordinated investigation, AI Canvas provides a shared operational workspace where teams and AI agents work together to investigate and take action to resolve it.

note.svg

Cisco Cloud Control is Generally Available in the United States only. Support for additional regions will be added in future milestones.

What Cisco Cloud Control offers

  • One login: Move across connected Cisco products without losing context.

  • One inventory and topology: View sites, assets, health, and connections across connected Cisco products in one place.

  • One view for alerts: Review alerts that Cisco Cloud Control correlates across IT domains, along with the recommended next steps. Review the available context, take an authorized action, or continue the investigation in AI Canvas.

  • One agentic workspace: Work with AI agents in a shared workspace to review evidence, understand cause and impact, and investigate and resolve issues across IT domains.

  • One assistant: Use AI Assistant (homepage or sidebar) for quick answers and tasks across domains.

  • Governed AI operations: AI agents operate within the permissions, policies, and boundaries your organization defines, with centralized governance, auditability, and appropriate human oversight built in.

Get started with Cisco Cloud Control

To get started with Cisco Cloud Control, complete these tasks:

  1. Complete prerequisites:

    1. Make sure you can access all your Cisco products with the same email address. If you use different email addresses or domains, ask your product admins to grant access to that one email address in each product.

    2. Complete the necessary readiness for the products to onboard Cisco Cloud Control.

  2. Onboard to Cisco Cloud Control:

    1. For each product you want to manage in Cisco Cloud Control, identify an admin who can sign in to the product and accept the terms and conditions.

    2. The admin signs in to the product they want to connect.

    3. The admin selects the tenants for that product and creates an environment.

After completing onboarding, refer to Cisco Cloud Control Overview to learn about the Cisco Cloud Control Home page, platform services, and capabilities.

Prerequisites

Product-specific prerequisites are listed under each product. Complete the prerequisites for the products you plan to onboard into Cisco Cloud Control.

note.svg

If a product is not listed in this section, no additional product-specific prerequisites are required.

ThousandEyes

ThousandEyes provides digital experience monitoring and visibility across applications, networks, and internet paths.

  • Ensure that the admin performing the onboarding has Organization Admin access to the required ThousandEyes orgs or another role that includes the Edit security & authentication settings permission.

  • For AI Canvas capabilities, ensure that AI Features is enabled in ThousandEyes. Sign in to ThousandEyes as an administrator, go to Manage > Account Settings > Organization Settings > AI Features, and turn on the features. For more information, refer to the ThousandEyes documentation.

Meraki

Meraki provides cloud-managed networking and centralized management for distributed network infrastructure.

Configure the SSO Login URL for IdP-initiated SAML

If your organization uses SAML SSO to sign in to Meraki, complete these steps:

  1. Confirm that the SSO Login URL is populated in Meraki Dashboard

    Sign in to Meraki Dashboard as an administrator and go to Organization > Settings > Authentication > SSO Login URL.

    1. Confirm that the SSO Login URL field is populated. If it is empty, contact your IdP admin to obtain the "SSO Login URL" for Meraki. Enter the URL in the SSO Login URL field, then select Save.

      To find the URL in your IdP:

      • Duo: In the Duo Admin Panel, go to Applications > Application and select the "Meraki SAML Application". Copy the SSO login URL from the application’s Metadata section.

      • Okta: In the Okta Admin Console, go to Applications and Resources > Applications > select the "Meraki SAML Application" > Sign On tab. Click "More details" and copy the Sign on URL from Metadata details.

      • Microsoft Entra: In the Entra admin center, go to Enterprise Applications > select the "Meraki SAML Application", then go to Manage > Single sign-on > Section 4 > copy the Login URL.

    2. Once receiving the URL, the Meraki admin enters it in the SSO Login URL field in Meraki Dashboard.

  2. For Microsoft Entra, configure the SSO Subdomain

    1. The Meraki admin signs in to Meraki Dashboard > Organization > Settings > Authentication.

      1. Enter a unique subdomain under SSO Subdomain and select Save.

      2. Send the subdomain to the Entra admin.

    2. The Entra admin adds the subdomain to the Meraki SAML application.

      In the Entra admin dashboard, go to Enterprise Applications > select the "Meraki SAML Application", then go to Manage > Single sign-on > Section 1 > Identifier (Entity ID) > Add identifier.

      C3-meraki-sso-prereq.jpg

For more information, refer to Provide your IdP’s SSO Login URL.

Meraki users with SAML SSO must verify their email

If you sign in to the Meraki dashboard using Security Assertion Markup Language (SAML) single sign-on (SSO), complete the following email verification steps to enable access to Cisco Cloud Control using your existing SAML authentication.

note.svg

This procedure applies only to users who sign in to the Meraki Dashboard using SAML SSO. It doesn’t apply to users who sign in with a local Meraki username and password.

  1. Sign in to Meraki using your SAML login.

    verify-email.jpg

  2. Select Verify email to confirm the email address you will use to access Cisco Cloud Control.

  3. Enter the email address for the Cisco account you’ll use to sign in to Cisco Cloud Control.
    Make sure you can receive email at this address, as a verification code will be sent to it.
    The email address you verify should:

    • Be your primary business email address.

    • Be associated with your Cisco account and will be used to sign in to Cisco Cloud Control.

    • Match the email address you use with other Cisco products you want to manage through Cisco Cloud Control.

      note.svg

      Your SAML login username may not be an email address. For example, some organizations use an employee ID or username to authenticate with their Identity Provider (IdP). During the verification step, always enter your Cisco-associated email address. For many organizations, this is also the email address used to sign in to the IdP Portal page.

  4. Complete email verification by entering the code sent to your email address.

note.svg

Troubleshoot SAML email verification

If you encounter the userNameType must be accountName error during email verification, both of these conditions might apply:

  • Your SAML user record has been flagged by Cisco Cloud Control onboarding as not yet verified or invalid.

  • You are a local Meraki admin using an email address that Meraki has verified.

Meraki does not allow the same email address for both a local account and a SAML account. Additionally, while Meraki does not require SAML users to have a valid email address, Cisco Cloud Control does. The error occurs when the email address matches one already associated with a verified local user.

To resolve the error:

  1. Delete your local user if it is no longer used. For more information, refer to Delete a Meraki-hosted User.

  2. If you need to keep the local user—for example, because you use it to generate API keys—edit its email address using plus addressing, also called subaddressing. SAML users cannot create API keys. Plus addressing creates an alias based on your existing email address.

    Email address changes can take up to five minutes to sync.

    To use a plus-addressing alias:

    1. Log in to the Meraki Dashboard using your local user credentials.

    2. Select My Profile.

    3. Under Your email address, change the email address to use the alias. For example, change name@company.com to name+alias@company.com, where alias is any text you choose.

      For more information, refer to:

  3. After resolving the email conflict, repeat the email verification process. If you changed the local user’s email address, use the updated address in Step 3.

Catalyst Center

Catalyst Center provides centralized management and automation for campus and branch networks.

  • Supported versions:

    • 2.3.7.11

    • 3.1.6 with GSMU 200 (General Availability)

    • 3.2.3 with GSMU 100 (General Availability)

    • 3.3.1 (Controlled Availability)

  • User permissions: SUPER-ADMIN-ROLE

  • User identity matching: The Catalyst Center username must match the user’s Cisco Cloud Control email identity. For example, if the user signs in to Cisco Cloud Control as user1@cisco.com, the Catalyst Center username must also be user1@cisco.com, rather than a short username such as user1. This consistency allows the user to be correctly correlated between Catalyst Center and Cisco Cloud Control.

    • External authentication (TACACS+/RADIUS): Configure the AAA or identity infrastructure so the user can authenticate to Catalyst Center with the same email address or UPN used in Cisco Cloud Control.

    • Local authentication: Create a Catalyst Center local user with the same Cisco Cloud Control email address as the username.

      • In Catalyst Center, go to Systems > Users & Roles > + Add User.

      • In the Add User dialog, enter the full email address (for example, user1@cisco.com) in the Username field.

  • Firewall requirements: Configure your firewall to allow the following FQDNs and port for connectivity to Cisco Catalyst Cloud. An FQDN (fully qualified domain name) is the complete internet name of a service, including its subdomain.

    • Port 443

    • FQDNs:

      • ciscoconnectdna.com

      • neoffers.cisco.com

      • neoffers-de.cisco.com

      • neoffers-sg.cisco.com

      • Dnaservices.cisco.com

      • dashboard.meraki.com

      • Api.meraki.com

Intersight

Cisco Intersight provides centralized visibility, automation, and lifecycle management for Cisco compute infrastructure across data centers and edge locations.

If you use SAML SSO to log into Intersight, follow these steps so you can access Cisco Cloud Control through Intersight:

  1. From the Intersight dashboard, select Settings > Authentication > Cisco ID.

  2. Configure your IdP to enable SAML SSO user access.

For more information, refer to Configure Cisco Cloud Control User Access in Intersight.

Nexus Dashboard

Nexus Dashboard provides centralized management and operations for data center networks and fabrics.

  • Cisco Cloud Control supports Nexus Dashboard version 4.x.

  • If you do not have an Intersight tenant and need one only to connect your Nexus Dashboard assets, visit https://www.intersight.com and create a new account.

Nexus Hyperfabric

Nexus Hyperfabric provides cloud-managed data center networking for deploying and operating Nexus-based fabrics.

To make Nexus Hyperfabric data available in Cisco Cloud Control, enable data sharing for the Nexus Hyperfabric organization.

  1. Log in to the Nexus Hyperfabric.

  2. Choose Administration > Organization settings.

  3. Enable data sharing.

Splunk Cloud

The Splunk integration with Cisco Cloud Control provides single sign-on, cross-launch between platforms, access to Splunk data and skills in AI Canvas, and Splunk AI Assistant capabilities through the Cisco Unified AI Assistant.

Before onboarding or connecting Splunk Cloud Platform to Cisco Cloud Control, confirm the following:

  • Splunk Cloud Platform stack runs version 10.5 or later.

  • Splunk Cloud stack is hosted on US Commercial AWS.

    Future Support: GCP, Azure, FedRamp, Gov Cloud

  • A Splunk user with the “sc_admin” role must:

    1. Install the latest versions of the following apps:

      1. Splunk MCP Server

      2. Splunk AI Assistant

    2. Assign the mcp_tool_execute capability to every role that requires Splunk access in AI Canvas.

      Navigate to Splunk Cloud Home > Settings > Roles > Capabilities to assign it.

  • Splunk users must verify their email addresses to complete their migration to Cisco Unified Identity.

    1. Version 10.5: Contact your sales team to enable email verification.

    2. Version 10.6 or later: Email verification is enabled by default when users log in.

note.svg

  • Identify any PCI, HIPAA, or other compliance requirements that may require reviewing the applicable Cisco terms.

  • For Splunk customers in the AWS US East region, identify any regional data requirements before connecting your Splunk environment to Cisco Cloud Control in the US West region.

Catalyst SD-WAN Manager

Catalyst SD-WAN Manager provides centralized management and monitoring for Cisco SD-WAN networks.

  • Catalyst SD-WAN Manager integrates with Cisco Cloud Control through Security, formerly known as Security Cloud Control.

  • Deployment support:

    • Supported: Catalyst SD-WAN Manager Cloud deployments

    • Planned: Catalyst SD-WAN Manager Cloud-Pro deployments

  • For information about supported Catalyst SD-WAN Manager releases, compatibility requirements, and onboarding to Security, contact SD-WAN Manager–Cisco Cloud Control compatibility support. The supported releases may change as compatibility requirements are updated.

  • Organizations outside the United States are not available for selection in the tenant switcher. This is intentional. Security filters non-US organizations to prevent their data from being processed by US-based Cisco Cloud Control services.

Cisco Spaces

Cisco Spaces provides end-to-end indoor location services and intelligence through a unified dashboard, helping organizations drive IT and business outcomes.

Ensure that the user performing the onboarding has the Cisco Spaces Dashboard Admin role.

note.svg

Customers who have chosen to implement SSO only with Cisco Spaces instead of implementing SSO with Cisco Common Identity (CCI) are not currently supported in Cisco Cloud Control. They can continue to access Cisco Spaces from the dashboard until they migrate their SSO to Cisco Cloud Control.

Supported browsers

Cisco Cloud Control supports these browsers:

  • Google Chrome

  • Mozilla Firefox

  • Apple Safari

  • Microsoft Edge

note.svg

If you encounter issues when cross-launching use a private window.

Onboard to Cisco Cloud Control

The onboarding process in Cisco Cloud Control lets you create an environment for the product tenants you want to manage. An environment brings tenants from multiple products into a shared Cloud Control experience, where your team can manage them and correlate data across them for monitoring and troubleshooting. Depending on the product, a tenant may represent an organization, account, network, stack, or another product-specific entity.

Before you begin, make sure you have admin access to the products and tenants you want to connect. Sign in to Cisco Cloud Control with the same email address you use across all Cisco products you want to manage.

  1. In Cisco Cloud Control, enter your work email, and select Continue.

    c3-onboarding-enter-email-address.jpg

    Cisco Cloud Control checks whether your email is approved for access. If it is not approved, you cannot continue onboarding. Select Contact sales to request access.

    On subsequent logins, if you want to log into Cisco Cloud Control using a different product than the one you selected initially:

    1. In the Welcome back dialog, select More options.

    2. Select a product, then select Sign in.

  2. The welcome screen introduces Cisco Cloud Control and how it brings Cisco products together. Watch the video, then select Get started.

    c3-onboarding-demo-video.jpg

  3. Choose a product to connect. When you sign in for the first time, you can connect only one product. Once signed in, you will be directed to the Products page in the Admin Console to add more products.

    c3-onboarding-choose-a-product.jpg
    note.svg

    The examples here use Meraki. Choose the product you want to connect from the available options.

  4. Sign in to the selected product when prompted.

  5. Select the product tenant or tenants you want to manage together. To find specific tenants, use the search field and select them. To select every tenant in the list, choose Select all. Then, select Next.

    c3-onboarding-select-tenants.jpg

    The tenants for the product you used to sign in to Cisco Cloud Control are displayed. You can select only tenants that you have admin access to and that are not already part of an environment. For Security and ThousandEyes, you can select only one tenant.

    note.svg

    Your data stays in its original product tenant. Connecting tenants lets Cisco Cloud Control correlate related data for monitoring and troubleshooting; it does not move or merge the data.

  6. Give a name to this environment that you and your team can recognize. An environment is a group of product tenants you manage together. Cisco Cloud Control provides shared view across them for monitoring, troubleshooting, and other Cloud Control experiences.

    c3-onboarding-name-environment.jpg

  7. Review your choices and confirm the environment name, connected product, and selected tenants.

    c3-onboarding-review-your-choices.jpg
    note.svg

    • Full admins of the selected tenants become admins of this Cisco Cloud Control environment. Other users are assigned the Member role.

    • Existing product roles and permissions stay the same.

    • Data remains separate, but can be correlated across the environment to deliver insights and findings.

  8. Review and accept the Terms & Conditions, then select Create environment.

  9. Wait while Cisco Cloud Control creates the environment and prepares your sign-in.

    note.svg

    If you see the message We could not open your environment. Please try signing in again., select Retry sign-in to continue.

    After Cisco Cloud Control creates your environment, the Home page opens.

  10. Open Products by selecting the Main menu app-launcher.jpg and then choosing Admin Console.

    This page shows connected products and additional products you can connect to the environment that you have admin access to.

    note.svg

    Access to this page requires the Environment Admin role.

    c3-onboarding-products-page.jpg
    note.svg

    For subsequent sign-ins using the same browser, Cisco Cloud Control returns you to the last environment you accessed.

  11. To connect another product, under Available to connect, select Connect next to that product. The Select tenants slider opens.

  12. In Eligible tenants, select the tenants you want to add.

    note.svg

    Only the product tenants for which you have admin access are displayed.

  13. Select Connect.

  14. Select Connect tenant to confirm this operation.

For more information, refer to Cisco Cloud Control Administration.

For steps to add other users and assign Cisco Cloud Control roles, refer to Manage users.

Post-onboarding setup

The procedures in this section are required only for the products listed here.

Connect Catalyst Center

Choose the setup path that matches your Meraki configuration:

Meraki non-SAML

Use this procedure to integrate Catalyst Center directly through Cisco Cloud Control.

  1. In Cisco Cloud Control, select the Main menu app-launcher.jpg and choose Admin Console.

  2. In Products, navigate to Browse All Products > On-premise products

  3. Select Set up on the Catalyst Center tile.

  4. Confirm that you meet the listed prerequisites, then select Connect.

  5. If you do not have a Meraki account associated with the email address you use to sign in to Cisco Cloud Control, follow the wizard to create one.

    1. When prompted, create a password for your Meraki Dashboard account.

    2. Verify your account using the verification email from Meraki.

    3. Log in to the Meraki dashboard.

    4. Return to the Cisco Cloud Control tab and select Next to continue adding Catalyst Center.

      note.svg

      After you create a new Meraki account, it can take approximately 5–10 minutes to become accessible from Cisco Cloud Control.

  6. In the Add Catalyst Center dialog, enter this information about your Catalyst Center deployment:

    • Display label

    • IP address or FQDN

    • Member ID. In Catalyst Center, select the help icon (?), go to About, and copy the Member ID.

      Then select Add Catalyst Center.

  7. Activate Catalyst Center’s integration with Cisco Cloud Control:

    1. In Catalyst Center, select System > Settings > External Services > Cisco Catalyst Cloud.

    2. Register to Catalyst Cloud if needed.

    3. Under Applications, find the Cisco Cloud Control and Meraki tile and select Activate.

  8. Return to the Cisco Cloud Control tab and select Refresh Page. The screen will update, indicating that Catalyst Center is now connected to Cisco Cloud Control.

    1. Select Close.

    2. In the Products page, confirm that the Catalyst Center product has a status of Connected. You can also see the controller’s updated status by selecting its Actions menu ellipsis.jpg and then selecting Refresh status.

  9. Confirm the user identity in Catalyst Center:

    1. In Catalyst Center, go to System > Users & Roles and verify that the username matches the user’s Meraki and Cisco Cloud Control email identity. For example, if the user signs in to Meraki and Cisco Cloud Control as user1@cisco.com, the Catalyst Center username must also be user1@cisco.com, not a short username such as user1.

    2. If the usernames do not match, use the applicable authentication method:

      • Local authentication: Create a Catalyst Center local user and set the username to the same email address used for Meraki and Cisco Cloud Control. In Catalyst Center, go to System > Users & Roles > + Add User. In the Add User dialog, enter the full email address (for example, user1@cisco.com) in the Username field.

      • External authentication (TACACS+/RADIUS): Configure the AAA or identity infrastructure so the user can authenticate to Catalyst Center with the same email address or UPN used in Cisco Cloud Control.

  10. Grant users access to the new Catalyst Center organization in Meraki:

    1. In Meraki, use the organization picker to select the new Catalyst Center org.

    2. Navigate to Organization > Administrators, select + Add Admin, and add the users who need access.

  11. After approximately 5–10 minutes, in Cisco Cloud Control, select the Main menu app-launcher.jpg and choose Admin Console.

    Confirm that the new Catalyst Center organization appears under Meraki and is part of the correct environment.

Meraki SAML with Global Overview

If your organization has more than one Meraki organization and uses SAML SSO to sign in, integrate Catalyst Center through Global in the Meraki Dashboard. When adding Catalyst Center, select an existing Meraki organization to clone. This copies its SAML settings to the new Catalyst Center organization.

  1. In Cisco Cloud Control, select the Main menu app-launcher.jpg and choose Meraki.

  2. In Meraki Dashboard, confirm that Global appears in the upper-left navigation. If it does not, use the procedure for Meraki SAML without Global Overview.

  3. Select Global > Overview, then select View new version.

  4. Select Add Organization > Add Catalyst Center as an organization.

    c3-onboarding-catc-integration-global.jpg

  5. In the Add Catalyst Center dialog, enter the deployment details.

    1. Select Clone an existing organization to copy its SAML settings from an existing SAML org.

    2. Select the cloud region to host the organization. Only US regions are supported.

    3. Enter the name of the new organization.

    4. Enter the Catalyst Center IP address or FQDN.

    5. Enter the Catalyst Center Member ID. In Catalyst Center, select the help icon (?), go to About, and copy the Member ID.

      Then select Add Catalyst Center.

  6. Activate Catalyst Center’s integration with Cisco Cloud Control:

    1. In Catalyst Center, select System > Settings > External Services > Cisco Catalyst Cloud.

    2. Register to Catalyst Cloud if needed.

    3. Under Applications, find the Cisco Cloud Control and Meraki tile and select Activate.

  7. Return to the Meraki tab and confirm that the Catalyst Center integration appears in the organization list.

  8. Confirm the user identity in Catalyst Center:

    1. In Catalyst Center, go to System > Users & Roles and verify that the username matches the user’s Meraki and Cisco Cloud Control email identity. For example, if the user signs in to Meraki and Cisco Cloud Control as user1@cisco.com, the Catalyst Center username must also be user1@cisco.com, not a short username such as user1.

    2. If the usernames do not match, use the applicable authentication method:

      • Local authentication: Create a Catalyst Center local user and set the username to the same email address used for Meraki and Cisco Cloud Control. In Catalyst Center, go to System > Users & Roles > + Add User. In the Add User dialog, enter the full email address (for example, user1@cisco.com) in the Username field.

      • External authentication (TACACS+/RADIUS): Configure the AAA or identity infrastructure so the user can authenticate to Catalyst Center with the same email address or UPN used in Cisco Cloud Control.

  9. After approximately 5–10 minutes, in Cisco Cloud Control, select the Main menu app-launcher.jpg and choose Admin Console.

    Confirm that the new Catalyst Center organization appears under Meraki and is part of the correct environment.

Meraki SAML with no Global Overview

If your organization uses Meraki SAML and Global does not appear in the Meraki Dashboard navigation, use a local Meraki account, if available, to integrate Catalyst Center through Cisco Cloud Control. Then copy the SAML settings from the existing Meraki organization to the new Catalyst Center organization.

  1. Sign out of Cisco Cloud Control, then sign in using a local Meraki admin account.

  2. In Cisco Cloud Control, select the Main menu app-launcher.jpg and choose Admin Console.

  3. In Products, navigate to Browse All Products > On-premise products

  4. Select Set up on the Catalyst Center tile.

  5. Confirm that you meet the listed prerequisites, then select Connect.

  6. In the Add Catalyst Center dialog, enter the following information about your Catalyst Center deployment:

    • Display label

    • IP address or FQDN

    • Member ID. In Catalyst Center, select the help icon (?), go to About, and copy the Member ID.

      Select Add Catalyst Center.

  7. Activate Catalyst Center’s integration with Cisco Cloud Control:

    1. In Catalyst Center, select System > Settings > External Services > Cisco Catalyst Cloud.

    2. Register to Catalyst Cloud if you have not already done so.

    3. Under Applications, find the Cisco Cloud Control and Meraki tile and select Activate.

  8. Return to the Cisco Cloud Control tab and select Refresh Page. The screen will update, indicating that Catalyst Center is now connected to Cisco Cloud Control.

    1. Select Close.

    2. In the Products page, confirm that the Catalyst Center product has a status of Connected. You can also see the controller’s updated status by selecting its Actions menu ellipsis.jpg and then selecting Refresh status.

  9. Confirm the user identity in Catalyst Center:

    1. In Catalyst Center, go to System > Users & Roles and verify that the username matches the user’s Meraki and Cisco Cloud Control email identity. For example, if the user signs in to Meraki and Cisco Cloud Control as user1@cisco.com, the Catalyst Center username must also be user1@cisco.com, not a short username such as user1.

    2. If the usernames do not match, use the applicable authentication method:

      • Local authentication: Create a Catalyst Center local user and set the username to the same email address used for Meraki and Cisco Cloud Control. In Catalyst Center, go to System > Users & Roles > + Add User. In the Add User dialog, enter the full email address (for example, user1@cisco.com) in the Username field.

      • External authentication (TACACS+/RADIUS): Configure the AAA or identity infrastructure so the user can authenticate to Catalyst Center with the same email address or UPN used in Cisco Cloud Control.

  10. Copy the SAML settings from the original Meraki organization:

    1. In Cisco Cloud Control, select the Main menu app-launcher.jpg and choose Meraki.

    2. In the organization picker, select the original Meraki org.

      c3-onboarding-meraki-org.jpg

    3. Navigate to Organization > Settings > Authentication.

    4. Copy the X.509 Cert SHA1 Fingerprint and SSO Login URL into a notepad.

    5. Navigate to Organization > Administrators > SAML and copy the names of the SAML groups you need to add to the new Catalyst Center organization in Meraki.

  11. Add the SAML settings to the new Catalyst Center org:

    1. In the organization picker, select the new Catalyst Center org.

    2. Select Organization > Settings and enter the X.509 Cert SHA1 Fingerprint and SSO Login URL you copied.

    3. Go to Organization > Administrators and create SAML groups using the group names you copied.

  12. Sign out of Cisco Cloud Control, then sign back in using the Meraki SAML email address.

    1. Select the Main menu and choose Meraki.

    2. In the organization picker, select the new Catalyst Center org.

  13. After approximately 5–10 minutes, in Cisco Cloud Control, select the Main menu and choose Admin Console. Confirm that the new Catalyst Center organization appears under Meraki and has been added to the correct environment.

Connect Splunk Cloud Platform

  1. As the Splunk Cloud Platform administrator, or as a user with the sc_admin role, sign in to Splunk Cloud Platform through the normal customer login path.

    splunk-login.jpg

  2. Confirm that all prerequisites, including email verification, have been completed.

  3. During the onboarding session, the onboarding team approves your access. After approval, a banner appears in Splunk Cloud Platform prompting you to set up Cisco Cloud Control. Select Set up Cloud Control.

    c3-splunk-home-setup-cloud-control.jpg

Connect Nexus Dashboard with Intersight

Connect a Nexus Dashboard instance to Cisco Cloud Control through Intersight to enable data sharing.

note.svg

If the Nexus Dashboard instance you want to add is already connected to Intersight, you do not need to complete this procedure. You only need to connect the associated Intersight tenant to Cisco Cloud Control.

Before you begin, ensure that:

  • At least one Intersight tenant is configured in Cisco Cloud Control.

  • You have the necessary permissions to claim a target device.

Follow the steps to connect the Nexus Dashboard instance to Cisco Cloud Control through Intersight. You can repeat these steps to add additional Nexus Dashboard instances to the same Intersight tenant.

  1. Log in to Nexus Dashboard directly, and select Admin > Nexus Dashboard management > Intersight.

    c3-nd-intersight-device-connector-page.jpg

  2. Copy the device ID and claim code listed for your instance.

  3. In Cisco Cloud Control, launch Nexus Dashboard.

  4. From the left navigation, select Clusters.

  5. Select Add Cluster.

    The wizard opens to guide you through connecting your Nexus Dashboard instance to Cisco Cloud Control through Intersight.

  6. Select Continue.

  7. Enter the device ID and claim code for your instance, and then select Continue.
    By default, the Nexus Dashboard instance is claimed by the Cisco Cloud Control tenant that you used to launch Nexus Dashboard.

    Your instance now appears on the Nexus Dashboard’s Clusters page.

note.svg

If Nexus Dashboard shows the instance as already claimed under Admin > Nexus Dashboard management > Intersight, but the instance does not appear in Cisco Cloud Control, verify that the Intersight account shown in Nexus Dashboard is the same Intersight tenant connected to Cisco Cloud Control. Also, in Intersight, select System > Targets and confirm that the Nexus Dashboard instance is listed.

Nexus Dashboard access management

Use the Admin Console to manage users’ access to Nexus Dashboard data across Cisco Cloud Control’s Inventory, Topology, Actions, and AI Canvas. Assign a Nexus Dashboard role based on each user’s access needs.

If a Cisco Cloud Control user has the:

  • Environment Admin or Environment Viewer role, they can see all assets managed by Nexus Dashboard in Inventory and Topology.

  • Member role, they can see data only for products they can access. To see Nexus Dashboard data in Inventory and Topology, assign the user the Observer or Fabric Administrator role in Nexus Dashboard.

To assign or update a user’s Nexus Dashboard role:

  1. Select the Main menu app-launcher.jpg and choose Admin Console.

  2. On the Users page, select Manage users, then select Manage Nexus dashboard access.

    c3-nd-access-on-cloud-control.jpg

  3. To grant access to a user, select +Assign. To change the assignment for an existing Nexus Dashboard user, select ellipsis.jpg > Manage assignment.

    1. In Assign user, select the Cisco Cloud Control user, then select Next.

    2. Select the Nexus Dashboard role to assign:

      • Fabric Administrator: Has full fabric management privileges.

      • Designer: Can modify configurations but cannot deploy them to network fabrics.

      • Approver: Can approve or deny submitted configuration changes when change control is enabled.

      • Observer: Has read-only access.

      • Support Engineer: Performs support tasks and can deploy or revert approved changes under change control, but cannot modify configurations.

    3. Indicate why you are assigning the role, then select Next.

    4. Confirm that the settings are correct, then select Save.

Need help?