Cisco Cisco Prime Network Services Controller Adaptor for DFA White Paper

 

 

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

Page 14 of 46 

The end-host (physical or virtual) network profiles for autoconfiguration are created on DCNM and stored in the 

LDAP database accessible through LDAP. In the semi-automation mode, DCNM is the authoritative instance for 

managing the fabricwide Segment ID with the appropriate tenant network profile parameters without a northbound 

orchestration. DCNM comes with multiple on-demand end-host (physical or virtual) network profiles. To provision 

the end-hosts, create a network in the DCNM and store it in the LDAP directory by accessing the DCNM Auto-

Configuration option from the main menu as shown in Figure 14. 

Figure 14.    Accessing the DCNM 7.0 Auto-Configuration Menu Option 

 

The autoconfiguration window is divided into two panes. 

The top pane allows the operator to define an organization and partitions within that organization. The first step is 

to create the organization. The next step is to create a partition for the organization. The DCNM automatically 

assigns a Layer 3 Segment ID (sometimes called a partition ID) from a predefined Layer 3 Segment ID pool (the 
default range is 50’000 to 60’000) that identifies the Layer 3 domain within the fabric. 

Note:   Please see the appendix for details about changing the default Segment ID pool in DCNM. 

The unique combination of partition within an organization represents a Layer 3 domain or a VRF. The VRF name 

is created by combining the organization name and the partition name (specifically vrfName = 

organizationName:partitionName). 

The example in Figure 15 shows an organization named ORG and with two partitions, named RED and BLUE. 

Figure 15.    DCNM 7.0 Top Pane for Creating an Organization and Partitions