The server-side configuration at a high level involves:

1. Creating a VLAN for the servers that are attached to the tenant. The server can be either a virtual or physical server. This VLAN is local to the leafs to which the server is connected.

2. Specifying a globally identifiable segment, which will be used to send traffic to these servers over the fabric.

3. Creating an SVI for servers to be able to talk to other servers.

4. Choosing the right fabric mode for the IP traffic; that is, if an enhanced forwarding using the proxy-gateway is required or a traditional forwarding using the anycast-gateway option.

configure terminal
	vlan 100 
	vn-segment 10000 
	mode fabricpath 
	interface vlan 100 
		vrf member xyz 
		ip address 10.1.1.1/24 
		ipv6 address 10:1:1::1/64 
		fabric forwarding mode [anycast-gateway | proxy-gateway]  
		no ip redirects 
		no ipv6 redirects
		no shutdown  

The fabric-side configuration at a high level involves:

1. Creating the required VRF for the tenant.

2. Setting the Layer-3 Segment or the VNI (as shown below) that is used for identifying the routed traffic of the tenant globally.

3. BGP route distribution to the route reflector.

The following steps detail the configuration steps:

1. Creating the VRF for the tenant—When a Layer-3 segment is configured, configuration corresponding to the Layer-3 segment is performed using a specific configuration profile. This configuration profiles must be available as part of the POAP of the leaf node. IP forward and IPv6 forward in this configuration profile indicates Layer-3 IPv4/IPv6 forwarding is required on this SVI.

   Note	The keyword 'VNI' in the VRF context helps to trigger this specific config-profile.

   A sample configuration is as follows:

   Configure profile vrf-tenant-profile
      vlan $vrfVlanId
          vn-segment $vrfSegmentId
          mode fabricpath
     interface vlan $vrfVlanId
      vrf member $vrfName
      ip forward
      no ip redirects
      ipv6 forward
      no ipv6 redirects
      no shutdown
   

2. VRF context tenant— Specify a partition for this tenant. Each tenant will be placed in its own VRF.

3. VNI 100000— Specify the Layer-3 segment ID of the tenant, which is used for routing traffic over the fabric to the different leafs.

4. rd auto—Specify the Route Distinguisher (RD) value. With fabric, the manual specification of RD becomes unnecessary. With this command a RD value is automatically generated by the BGP process for each VRF, using the fabric control segment IP address and the VRF ID of the VRF.

5. address family ipv4 unicast— Enable the IPv4 address family for BGP.

6. route-target both auto—Specify that the route targets automatically generated are both exported and imported on this leaf.

7. address family ipv6 unicast— Enable IPv6 address family for BGP.

8. route-target both auto—Specify that the route-targets automatically generated are both exported and imported on this leaf.

9. router BGP 100—Enable route distribution to the route reflector so that it is available in the other leaf nodes. Whatever is configured under BGP is relevant only for the end-host SVI and not applicable for the core-facing SVI.

10. vrf tenant—Specify the VRF name for which this distribution is configured.

11. address family IPv4 unicast— Enable the IPv4 address family for BGP.

12. redistribute hmm route-map redist-host— Any address resolution protocols that are learnt under an SVI in fabric forwarding mode can be distributed using BGP to the other leaf nodes.