Cisco Cisco Intelligent Automation for Cloud 4.0 Technical Manual

For reference, although not described specifically in this document, here is a visual representation where two
UCS PODs, each with their own vCenter can have one Cisco IAC and two Nexus1000v virtual switches.

The sample steps provided were for proof−of−concept testing with the intention to provide a working
example. The goal was to model a deployment support two Nexus1000v virtual switches one instance of
Cisco IAC and PNSC. Provisioning was done only for Advanced Network Service enabled Organization and
VDCs under those Organizations.

Using a single Cisco IAC and PNSC, resources were discovered and registered; networks were built up as
well as PODs and containers in a proactive manner with selections being specific to each Datacenter. The end
result is the ability to deploy an Organization into one Datacenter (IT/Support) and then another Organization
under another Datacenter (IT/Support−II). Both of these Organizations exist under the same Tenant from
Cisco IAC and PNSC's perspective although they don't have to.

The end result is the ability for the administrator to have a choice to deploy Advanced Network Service
devices to one Datacenter or another. Through the proactive setup of networks, PODs and Containers, the
administrator now has a choice to deploy Advanced Network Service devices to one Datacenter or another.

Upon ordering a VDC, the appropriate Compute POD must be selected. There is flexibility in terms of which
datastore and cluster to deploy VMs to per VDC (described later). Beyond this point, ordering VMs and using
Virtual Network Services (Floating IP, Server Load Balancer Binding) have no dependencies in terms of
being in a second Datacenter with a second Nexus1000v.

Two Datacenters (Support and Support−II) are in use within one vCenter. Each Datacenter has their own
VSM and each has a single ESXi host acting as the VEM module for each VSM.