Prerequisites and Guidelines
This chapter covers deployment of a 3-node Multi-Site Orchestrator cluster. If you want to set up a single-node Orchestrator (for example, for testing purposes), follow the instruction in the Installing Single Node Orchestrator chapter instead.
Application Services Engine
You must have Cisco Application Services Engine installed and the cluster configured in Fabric External Mode as described in Cisco Application Services Engine User Guide.
Cisco Application Service Engine itself can be deployed using a number of different form
factors, such as a Cisco Application Service physical appliance (.iso
), in
a VMware ESX virtual machine (.ova
), in Amazon Web Services
(.ami
), or in Linux KVM (.qcow
), all of which are
supported for Multi-Site Orchestrator installations. Keep in mind however, you must use the
same form factor Service Engine for all Orchestrator nodes, mixing different form factors
within the same Orchestrator cluster is not supported.
Note that if you are deploying Services Engine in AWS, by default only PEM-based login is enabled for each node. If you'd like to be able to SSH into the nodes using a password, you will need to explicitly enable password-based logins. You can do that by logging into each node separately using the PEM file the first time, then executing the following command:
# acidiag login prompt enable
Internal Service Engine Networks
When first configuring Application Services Engine, two of the parameters that you provide are Application Overlay Network and Service Network.
The application overlay network defines the address space used by the application's services running in the Service Engine, such as the Multi-Site Orchestrator. Each Orchestrator node is assigned an IP address from this network, which is then used to communicate with each site's Cisco APIC. The services network is an internal network used by the Service Engine and its processes.
Both of these networks must be unique and not overlap with any other services in your environment.
Network Time Protocol (NTP)
Multi-Site Orchestrator uses NTP for clock synchronization, so you must have an NTP server configured in your environment. NTP server information is provided as part of the Application Services Engine installation procedure.
Application Services Engine Requirements
The following table summarizes the Application Services Engine requirements for Cisco ACI Multi-Site Orchestrator.
Orchestrator Version | Requirements | ||
---|---|---|---|
Release 2.2(3) and 2.2(4)
|
Cisco Application Services Engine, Release 1.1.2i If the Application Services Engine is deployed in an ESX or KVM virtual machine, the following additional requirements apply:
|