Cisco Cisco Prime Network Services Controller Adaptor for DFA 产品宣传页

 

 

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

Page 11 of 45 

The first obvious difference is the presence of service keyword in the name of the profile. Also, notice that unlike in 

the profile in the previous example, there is no Dynamic Host Configuration Protocol (DHCP) relay configuration 

because this profile assumes that the IP address of the appliance will be statically defined. There is also no 

forwarding mode specified, because the interfaces defined with this profile will be configured as normal switch 

ports, and subsequently the SVI for such a VLAN is used for route peering with the attached appliance. No end 

hosts or workloads should be attached to network segment defined by this profile. In addition, the included partition 

profile is different: include profile vrf-common-FW. 

configure profile vrf-common-FW 

   vrf context $vrfName   

## same as in previous example unless otherwise 

specified

 

    vni $include_vrfSegmentId    

    rd auto 

     address-family ipv4 unicast 

     route-target import %BORDER_LEAF_RT 

     route-target both auto 

    address-family ipv6 unicast 

     route-target import %BORDER_LEAF_RT 

     route-target both auto 

    router bgp $asn 

     vrf $vrfName 

      address-family ipv4 unicast 

       redistribute hmm route-map FABRIC-RMAP-REDIST-HOST 

       redistribute direct route-map FABRIC-RMAP-REDIST-SUBNET 

       maximum-paths ibgp 2 

       redistribute ospf 5 route-map ospfMap  

## redistribute all dynamically 

learned OSPF prefixes into BGP.

 

      address-family ipv6 unicast 

       redistribute hmm route-map FABRIC-RMAP-REDIST-HOST 

       redistribute direct route-map FABRIC-RMAP-REDIST-SUBNET 

       maximum-paths ibgp 2 

exit 

Now that you know some of the basic concepts of network and partition autoconfiguration profiles, you can begin to 

plan and configure network service integration.  

This section presents several typical deployment scenarios and autoconfiguration profiles to use to implement 

them. Table 2 at the end of this section summarizes all mandatory and optional configurable options for the 

autoconfiguration profiles discussed here. Full command-line interface (CLI) configurations for these 

autoconfiguration profiles are presented in the appendix. 

For a step-by-step deployment example, refer to the next section. 

The information in this section is provided in the following format: 

● 

Graphical representation of a sample deployment case and respective autoconfiguration profile 

● 

Expected configuration parameters on connected devices