Cisco Cisco Prime Network Services Controller Adaptor for DFA White Paper

 

 

© 2014 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. 

Page 28 of 37 

Figure 39 illustrates the control loop for orchestration and device autoconfiguration when a Cisco Nexus 1000V 

Switch is used. Physical hosts use DHCP MAC address learning to identify segments. 

Figure 39.    Autoconfiguration Control Loop 

 

The sequence of events that can occur and cause a new workload to be provisioned is as follows: 

1.  Tenants (organizations), partitions, and network IDs (segments) are defined and deployed by the orchestrator 

(represented by T1 in Figure 39). 

2.  The segment is pushed by the orchestrator to the Cisco Nexus 1000V virtual supervisor module (VSM) or 

Open Virtual Switch (OVS).

10

 

3.  For VCD orchestration, the Cisco Prime DCNM orchestration agent listens to an AMQP server event, fetches 

the tenant (organization) partition and network ID from the orchestrator or controller, and stores the data in the 

LDAP directory (DB) by using Cisco Prime DCNM REST APIs. Alternatively, the orchestrator can push the 

data directly via REST APIs. 

4.  Once the workload is deployed to a host, the Cisco Nexus 1000V negotiates with the leaf switch using Virtual 

Station Interface (VSI) Discovery and Configuration Protocol (VDP). The result is a locally assigned VLAN on 

the switch and creation of a Virtual Routing and Forwarding (VRF) instance for that segment ID. 

5.  The leaf node fetches the configuration profile from the LDAP server in the Cisco Prime DCNM OVA to 

provision the new segment.  

                                                 

10

 If the host is a physical host and not a virtual machine, the system can identify the correct network through DHCP MAC 

address learning. In this scenario, the orchestrator must coordinate the mapping of the physical host to the network ID (segment).