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 12 of 46
In Cisco Unified Fabric with autoconfiguration, the leaf switch acts as a LDAP client. This LDAP client queries the
LDAP server (typically hosted in DCNM) for specific objects, which will subsequently be downloaded to the leaf
switch after an autoconfiguration instantiation trigger event. The autoconfiguration instantiation eliminates the need
to provision and clean up static end-host (physical or virtual) and edge-device configurations on the leaf switches.
Two commands are required to make the leaf switch an LDAP client to support autoconfiguration. The first
command is required to query the networks table, and the second command is required to query the profiles table.
The network query returns the network parameters ($values called configArgs or Configuration Arguments) along
with the configuration profile referenced by the network. The profile query returns the contents of the referenced
configuration profile if not already cached on the leaf switch.
The specified IP address in the configuration example in Figure 12 is the out-of-band IP address of DCNM with the
LDAP service running on it. The LDAP database can also be accessed in-band.
Figure 12. LDAP Client Configuration Example
Example on a Leaf Switch
!
fabric database type network
server protocol ldap ip 192.168.100.250 vrf management
db-table ou=networks,dc=cisco,dc=com key-type 1
fabric database type profile
server protocol ldap ip 192.168.100.250 vrf management
db-table ou=profiles,dc=cisco,dc=com
!
Note: The LDAP client configuration for the two object classes namely, network and profile, is part of the
POAP definition and is executed during the day-zero deployment process on all leaf switches.
Autoconfiguration Overview
Autoconfiguration is a powerful feature that helps provision tenant profiles just-in-time on the Cisco Unified Fabric.
Cisco Unified Fabric with autoconfiguration helps simplify server deployment by centralizing the network
configuration and allows just-in-time reconfiguration in the event that a server moves to another leaf switch in the
fabric.
Autoconfiguration can be deployed in any of the following three modes, or a combination:
1. Semi-Automation
2. Fully-Automation
3. Manual
Semi-Automation mode, or partial automation, can be used for physical hosts and virtual machines where DCNM is
employed as a pseudo-orchestrator. Semi-automation mode supports instantiation through VDP as well as using
ARP, ND, DHCP or any other packet with a IEEE 802.1q tag.
Full-automation mode uses an orchestrator connected northbound to DCNM. The orchestrator allows the network
operator to access, provision, and automate compute, storage, and network resources and supports physical and
virtual machine network profile instantiation.