Cisco Nexus Dashboard
Cisco Nexus Dashboard
Aiman Alnoamani
CCDE , 2xCCIE EI and DC
https://www.linkedin.com/in/aymen-salem-alnoamani-770b801b/
Cisco Nexus Dashboard. A single platform for full-lifecycle data center automation. Today's data
center is anywhere the data is. Increased complexity in ITOps with hyperconnected users and
devices.
• Orchestrator (NDO): this is serviced is important for deploying and managing ACI Multi-Site
between many sites.
• Network Insights (NDI): Big data analytics platform, this The platform offers extensive
insights functionality, such as dynamic correlation, impact analysis, proactive alerts, failure
prediction and remediation. By collecting and processing telemetry data from NX-OS and ACI
Nexuses 9000
• Fabric Controller (NDFC): It is a policy controller for NX-OS devices to simplify the
configuration L2/L3 vPC and VXLAN BGP EVPN fabrics between switches.
• Nexus Data Broker: it is Centralized tool for managing for TAP/SPAN data replication around
the network infrastructure.
The data broker controller can be deployed in the following modes:
● Embedded: The controller is deployed on the TAP aggregation (NDDB) switch using guest
shell. In this mode, the solution can only be used as a single switch deployment.
Now let’s go to NDO
This service is the intersite policy manager. The NDO is a single-pane management, can enable
you to monitor the health-score state for all the interconnected sites.
NDO can help you to define, in a centralized place, all the intersite policies that you can push
them to different ACI fabric sites for rendering them on the physical switches building those
fabrics.
It therefore offers substantial control regarding when and where to implement those policies,
thus enabling the domain separation of changes that distinctly defines the Cisco ACI Multi-
Site architecture.
ACI Multi-Site Use Cases
This use case is typical for disaster recovery sites where there’s 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.
A new BD, called DB-BD, will be provisioned to both the San Francisco and New York sites,
and enables this use case on the Pseudoco tenant.
4- 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’s a requirement to connect the existing fabric to
a new Greenfield ACI environment using the Nexus Dashboard 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.
References:
https://www.cisco.com/c/en/us/products/collateral/cloud-systems-management/multi-site-
orchestrator/nb-06-mso-so-cte-en.html
Cisco Application Centric Infrastructure - Cisco ACI Multi-Site Architecture White Paper - Cisco
https://www.cisco.com/c/en/us/solutions/collateral/data-center-virtualization/application-centric-
infrastructure/white-paper-c11-739609.html