You can deploy the Cisco DCNM installer in one of the following modes:
Supported Latency
The supported latency for Cisco DCNM LAN Fabric deployment is defined below:
-
Between Native HA Primary and Secondary appliances, latency is 50ms.
-
Between DCNM Native HA Primary appliance to Switches, latency is 50ms.
-
Between DCNM Computes latency is 50ms.
Standalone Server
All types of installers are packaged along with PostgreSQL database. The default installation steps for the respective installers
result in this mode of deployment.
Note |
We recommend that you deploy Cisco DCNM in Native HA Mode.
|
High Availability for Virtual Appliances
You can deploy the DCNM Virtual appliances, both OVA and ISO, in High Availability mode to have resilience in case of application
or OS failures.
DCNM Computes
Compute nodes are scale out application hosting nodes that run resource-intensive
services to provide services to the larger Fabric. When compute nodes are added, all
services that are containers, run only on these nodes. This includes Config
Compliance, Endpoint Locator, and Virtual Machine Manager.
DCNM in Clustered Mode
In a clustered mode, the Cisco DCNM Server with more compute nodes provides an
architecture to expand resources, as you deploy more applications. The DCNM Servers
do not run containerized applications. All applications that work in unclustered
mode works in the clustered mode, also.
DCNM in Unclustered Mode
In unclustered mode, the Cisco DCNM runs some of its internal services as containers.
Cisco DCNM leverages resources from the Standby node for running some containers
applications. The Cisco DCNM Active and Standby nodes work together to extend
resources to the overall functionality and deployment of DCNM and its applications.
However, it has limited resources to run some of the advanced applications and to
extend the system to deploy more applications delivered through the Cisco AppCenter.