Cisco ACI with Cisco AVS

Log into the Cisco APIC.

On the menu bar, click Fabric > Access Policies.

In the Policies navigation pane, click Quick Start, and then in the central pane click Configure an interface, PC, and VPC.

In the Configure Interfaces, PC, and VPC dialog box, expand Configured Switch Interfaces, click the green + icon, and then perform the following steps:

1. In the Select Switches to Configure Interfaces area, make sure that the Quick radio button is selected.

2. From the Switches drop-down list, choose the appropriate leaf ID.

   In the Switch Profile Name field, the switch profile name automatically appears.

3. Click the green + icon again.

   The Configure Interfaces, PC, and VPC dialog box displays a wizard that enables you to configure interface, switch, and vCenter domain profiles.

In the wizard, perform the following actions:

1. In the Interface Type area, choose the appropriate radio button.

   PC or VPC are the only valid options for Cisco AVS deployment. See the section Guidelines for Creating Interface and Switch Policies in this guide.

2. In the Interfaces field, enter the interface or interface range for your vSphere hosts.

   Once you enter the interface or interface range, the wizard enters a name in the Interface Selector Name field.

3. In the Interface Policy Group area, choose the Create One radio button.

   Note	This procedure assumes that you are creating interface and switch policies and creating a vCenter domain from scratch. If you choose the Choose One radio button, you will not be able to do so in the wizard.

4. From the CDP Policy or the LLDP Policy drop-down list, create a policy.

   Note	If you use a Cisco Unified Computing System (UCS) server, create a policy to enable a Cisco Discovery Protocol (CDP) policy and a policy to disable Link Layer Discovery Protocol (LLDP).

   Note

   Beginning with Cisco AVS Release 5.2(1)SV3(1.15), CDP and LLDP policies are disabled by default. You must enable them in the configuration wizard. Enable CDP or LLDP policies in the Interface Policy Group area to enable them on Cisco AVS and other switches in the fabric. If you want to enable CDP or LLDP only on Cisco AVS, enable them in the vSwitch Policy area of the configuration wizard.

5. From the Link Level Policy drop-down list, choose the desired link level policy or create one.

   The link level policy specifies the speed of the physical interface. If you do not choose a link level policy, the speed will default to 10 Gbps.

6. In the Port Channel Policy drop-down list, choose Create Port Channel Policy.

   You need to choose the same policy that is on the ESXi server. For example, if the server does not support LACP, you can choose Static Channel - Mode On or MAC Pinning.

7. In the Attached Device Type area, choose AVS VLAN Hosts or AVS VXLAN Hosts.

   Note

   If the hypervisors are directly connected to leaf switches, you can use either VLAN or VXLAN. (Cisco UCS blade servers, where Fabric Interconnects are connected to the fabric, are considered to be directly connected.) However, if the hypervisors are not directly connected to leaf switches, you must use VXLAN. For more information, see the Overview section.

8. In the Domain area, make sure that the Create One radio button is chosen.

   The Create One option is used when creating a new VMM domain for an interface or switch profile, as you do in this procedure. The Choose One button is used when creating an interface or switch profile for a new host that you want to make part of an existing VMM domain.

9. In the Domain Name field, enter the domain name.

   Note

   When you create the VMM domain, you choose VLAN or VXLAN encapsulation, depending on the attached device type you chose in Step 5g. However, beginning with Cisco AVS Release 5.2(1)SV3(2.5), you can configure a single VMM domain to use VLAN and VXLAN encapsulation. After you finish installing the Cisco AVS, you can enable mixed encapsulation mode. See the section "Mixed-Mode Encapsulation Configuration" in the Cisco Application Virtual Switch Configuration Guide.

10. If you chose AVS VLAN Hosts in Step 5 g, in the VLAN Range field, enter the VLAN range as appropriate.

    Note	Do not define a range that includes the reserved VLAN ID for infrastructure network because that VLAN is for internal use.

11. If you chose AVS VXLAN Hosts in Step 5 g, in the Fabric Multicast Address field, enter an address, such as 225.1.1.1.

12. If you chose AVS VXLAN Hosts in Step 5 g, in the Pool of Multicast Address Ranges field, create a new multicast pool or choose an existing one.

    Note	The multicast address configured in Step 5 l must not overlap with the ranges configured in Step 5 m.

13. If you chose AVS VXLAN Hosts in Step 5 g, in the Local Switching area, choose True or False.

    With local switching, traffic within an endpoint group (EPG) does not go to the leaf, so if you choose local switching, you might not see some traffic counters. If you want to see all intra-EPG traffic, you should choose False. See the section Cisco Application Virtual Switch Overview for additional information about Local Switching and No Local Switching modes.

14. (Optional) From the Security Domains drop-down list, choose or create a security domain.

15. In the vCenter Login Name field, enter the vCenter Administrator/root username.

16. In the Password field, enter the vCenter Administrator/root password.

17. In the Confirm Password field, reenter the password.

Click the + icon to expand vCenter, and in the Create vCenter Controller dialog box, perform the following actions:

1. In the Name field, enter a name to refer to the vCenter domain.

   The name does not need to be the same as the vCenter domain name; you can use the vCenter host name.

2. In the Host Name (or IP Address) field, enter the host name or IP address.

   If you use the host name, you must already have configured a DNS policy on Cisco APIC. If you do not have a DNS policy configured, enter the IP address of the vCenter server.

3. From the DVS Version drop-down list, choose a DVS version.

   The DVS version that you choose represents the minimum ESXi version of the host that can be added to the virtual switch. So if you choose DVS version 5.5, you can add or manage hosts of ESXI version 5.5 and later.

4. In the Datacenter field, enter the data center name.

   Note	The name that you enter for Datacenter must match exactly the name in vCenter. The name is case sensitive.

5. Click OK.

   Note	For the following three steps, if you do not specify port channel, vSwitch, or interface control policies, the same interface policy that you configured earlier in this procedure will take effect for the vSwitch.

6. From the Port Channel Mode drop-down list, choose a mode.

   Choose MAC Pinning if you have a Unified Computing System (UCS) Fabric Interconnect (FI) between the top-of-rack switch and the Cisco AVS.

7. In the vSwitch Policy area, choose a policy.

8. In the Interface Controls area, choose BPDU Guard, BPDU Filter, or both.

9. From the Firewall drop-down list, choose Learning, Enabled or Disabled mode.

   Learning mode, the default, should be used only when upgrading from a version of Cisco AVS that does not support Distributed Firewall to a version that does. Otherwise, Distributed Firewall should be in Enabled mode.You can change the Distributed Firewall mode later. See the section Creating a Distributed Firewall Policy or Changing its Mode Using the GUI in this guide for instructions.

In the Configure Interface, PC, And VPC dialog box, click SAVE, click SAVE again, and then click SUBMIT.

Verify the new domain and profiles, by performing the following actions:

1. On the menu bar, choose Virtual Networking > Inventory.

2. In the navigation pane, expand VMM Domains > VMware > Domain_name > Controllers, and then choose the vCenter.

Log in to the Cisco APIC.

Go to Virtual Networking > Inventory > VMM Domains > VMware.

In the navigation pane, choose the relevant VMM domain.

In the VMM domain work pane, scroll to the VSwitch Policies area, and from the appropriate vSwitch policy drop-down list, choose the policy that you want to apply as an override policy.

Click Submit.

Log in to the VMware vSphere Web Client.

Choose Hosts and Clusters.

Choose the host on which to deploy the Cisco VSUM OVA.

From the Actions menu, choose Deploy OVF Template.

In the Deploy OVF Template wizard, complete the information as described in the following table.

Pane	Action
1a Select source	Choose the Cisco VSUM OVA.
1b Review details	Review the details.
1c Accept License Agreements	Review the agreement and click Accept.
2a Select name and folder	Enter a name and choose a location for the appliance.
2b Select a resource	Choose the host or cluster to run the OVA template.
2c Select storage	Choose the data store for the VM. Choose either Thin provisioned format or Thick provisioned format to store the VM virtual disks. We recommend that you store the VM virtual disks in the Thick provisioned format.
2d Setup networks	Choose the destination network for the VM that is reachable from the vCenter Server.
2e Customize template	Provide the following information: Management IP address Subnet mask Gateway IP address DNS server IP address DNS entry to resolve the fully qualified domain name (FQDN) vCenter IP or FQDN vCenter username vCenter password HTTP cleartext port and HTTPS port
3 Ready to complete	Review the deployment settings. Caution  Any discrepancies can cause VM booting issues. Carefully review the IP address, subnet mask, gateway information, and vCenter credentials.

Click Finish.

After Cisco VSUM deploys successfully, click Close.

Power on the Cisco VSUM VM.

It might take 5 minutes for Cisco VSUM to be installed and registered as a vSphere Web Client plug-in.

Log in to the VMware vSphere Web Client.

Choose Home > Cisco Virtual Switch Update Manager.

In the Cisco Virtual Switch Update Manager pane, choose AVS > Upload.

In the Upload Switch Image pane, click Upload.

In the Virtual Switch Image File Uploader window, click Browse, choose the appropriate image folder available on your local machine, and then click Upload.

In the dialog box telling you that the .zip image folder was successfully uploaded, click OK.

You can confirm the upload in the Manage Uploaded switch Images pane.

Log in to the VMware vSphere Web Client.

Choose Home > Cisco Virtual Switch Update Manager.

In the Cisco Virtual Switch Update Manager pane, choose AVS > Configure, choose a data center, choose the Cisco AVS, and then click Manage.

You choose the Cisco AVS from the Choose an associated Distributed Virtual Switch area.

In the switch pane, choose Cisco AVS > Add Host-AVS.

In the Add Host-AVS tab, complete the following actions:

1. From the Target Version drop-down list, choose the target VIB version to be installed on the host.
   

   
   
   

2. Click Show Host.
   

   
   
   

   The hosts are represented in the following categories:

   • Cluster—Hosts that are part of clusters.

   • Standalone—Hosts that are not part of clusters. You can add hosts that are in a standalone mode.

3. Expand Cluster or Standalone, depending on your setup.

   Hosts are further organized within the Cluster and Standalone categories:

   • Supported—Hosts that are supported by the Cisco AVS. You can add these hosts.

   • Unsupported—Hosts that are not supported by the Cisco AVS.

   • Unreachable—Hosts that are in a not responding state or are in a disconnected state.

   • Already in DVS—Hosts that are already associated with the DVS. You cannot add a host that is already associated with a DVS.

   • No free PNIC—Hosts that do not have a free PNIC. You cannot add a host that does not have a free PNIC.

4. Choose one or more available hosts and then click Suggest.
   

   
   
   
   The PNIC Selection area displays the available uplinks for each host.

5. In the PNIC Selection area, choose the PNIC or PNICs to be added to the Cisco AVS.
   

   
   
   

6. Click Finish to add the host or hosts to the Cisco AVS.

Check the status of adding the host by completing the following steps:

1. Choose the host in the left navigation pane.

2. Click the Monitor tab and then click Tasks.
   

   
   
   

   The task console appears in the work pane, displaying a list of tasks with the most recent task at the top.

3. Find the task in the Task Name column and then view the status in the Status column.

   The Status column shows whether the task is complete or in progress.

   Note	Several tasks might appear above the primary task you just performed. They might be associated with your primary task. The host addition is confirmed when the primary task Add hosts to Cisco DVS has the status Completed.

On the menu bar, choose Tenants and the tenant where you want to create an EPG.

In the navigation pane, expand the folder for the tenant, the Application Profiles folder, and the folder for the application profile.

Right-click the Application EPG folder, and in the Create Application EPG dialog box, perform the following actions:

1. In the Name field, add the EPG name (db).

2. In the Bridge Domain field, choose the bridge domain from the drop-down list (bd1).

3. Check the Associate to VM Domain Profiles check box. Click Next.

4. In the STEP 2 > Domains area, expand Associate VM Domain Profiles and from the drop-down list, choose the desired VMM domain.

5. From the Deployment Immediacy drop-down list, accept the default or choose when policies are deployed from Cisco APIC to the physical leaf switch.

6. From the Resolution Immediacy drop-down list, choose when policies are deployed from the physical leaf switch to the virtual leaf.

   If you have Cisco AVS, choose Immediate or On Demand; if you have Cisco ACI Virtual Edge or VMware VDS, choose Immediate, On Demand, or Pre-provision.

7. (Optional) In the Delimiter field, enter one of the following symbols: |, ~, !, @, ^, +, or =.

   If you do not enter a symbol, the system uses the default | delimiter in the VMware portgroup name.

8. If you have Cisco ACI Virtual Edge or Cisco AVS, from the Encap Mode drop-down list, choose an encapsulation mode.

   You can choose one of the following encap modes:

   • VXLAN—This overrides the domain's VLAN configuration, and the EPG uses VXLAN encapsulation. However, a fault is for the EPG if a multicast pool is not configured on the domain.

   • VLAN—This overrides the domain's VXLAN configuration, and the EPG uses VLAN encapsulation. However, a fault is triggered for the EPG if a VLAN pool is not configured on the domain.

   • Auto—This causes the EPG to use the same encapsulation mode as the VMM domain. This is the default configuration.

9. If you have Cisco ACI Virtual Edge, from the Switching Mode drop-down list, choose native or AVE.

   If you choose native, the EPG is switched through the VMware VDS; if you choose AVE, the EPG is switched through the Cisco ACI Virtual Edge. The default is native.

10. Click Update and then click Finish.

In the Create Application Profile dialog box, create two more EPGs. Create the three EPGs—db, app, and web—in the same bridge domain and data center.

Log in to Cisco APIC.

Go to Fabric > Access Policies.

In the Policies navigation pane, expand the Pools folder.

Right-click the VLAN folder and then choose Create VLAN Pool.

In the Create VLAN Pool dialog box, in the Name field, give the VLAN pool a name.

In the Allocation Mode area, choose Dynamic Allocation or Static Allocation mode.

In the Encap Blocks area, click the + icon.

In the Create Ranges dialog box, in the Range area, type the numbers of the appropriate VLANs in the From and To fields.

In the Allocation Mode area, choose Dynamic Allocation, Inherit allocMode from parent or Static Allocation.

Click OK.

In the Create VLAN Pool dialog box, click Submit.

Log in to the vCenter.

Navigate to the virtual machine (VM) in the navigation pane.

Right-click the VM in the navigation pane.

In the Edit Settings dialog box for the VM, complete the following actions:

1. From the Network Adapter 1 drop-down menu, choose the appropriate combined value for tenant, application profile, and endpoint group (EPG).

   For example, you might see an option similar to T2|ap4|EPG1 followed by the values that were configured in Cisco APIC.

2. Repeat Step 4 a for any other network adapters you have and want to configure.

   You must configure one network adapter; configuring others is optional.

3. Click OK.

On the menu bar, choose TENANTS. In the Navigation pane, expand the tenant > Security Policies, right-click Filters, and click Create Filter.

In the Create Filter dialog box, perform the following actions:

1. In the Name field, enter the filter name (http).

2. Expand Entries, and in the Name field, enter the name (Dport-80).

3. From the EtherType drop-down list, choose the EtherType (IP).

4. From the IP Protocol drop-down list, choose the protocol (tcp).

5. From the Destination Port/Range drop-down lists, choose http in the From and To fields. (http)

6. Click Update, and click Submit.

   The newly added filter appears in the Navigation pane and in the Work pane.

Expand Entries in the Name field. Follow the same process to add another entry with HTTPS as the Destination port, and click Update.

On the menu bar, choose TENANTS and the tenant name on which you want to operate. In the Navigation pane, expand the tenant > Security Policies.

Right-click Contracts > Create Contract.

In the Create Contract dialog box, perform the following tasks:

1. In the Name field, enter the contract name (web).

2. Click the + sign next to Subjects to add a new subject.

3. In the Create Contract Subject dialog box, enter a subject name in the Name field. (web)

4. Note	This step associates the filters created that were earlier with the contract subject.

   In the Filter Chain area, click the + sign next to Filters.

5. In the dialog box, from the drop-down menu, choose the filter name (http), and click Update.

In the Create Contract Subject dialog box, click OK.

Create a VLAN domain (which contains a set of VLANs that are allowable in a set of ports) and allocate VLAN inputs, as follows:

apic1# configure
apic1(config)# vlan-domain dom_exampleCorp
apic1(config-vlan)# vlan 50-500
apic1(config-vlan)# exit

Once the VLANs have been allocated, specify the leaf (switch) and interface for which these VLANs can be used. Then, enter "vlan-domain member" and then the name of the domain you just created.

apic1(config-vlan)# leaf 101
apic1(config-vlan)# interface ethernet 1/2-4
apic1(config-leaf-if)# vlan-domain member dom_exampleCorp
apic1(config-leaf-if)# exit
apic1(config-leaf)# exit

Create a tenant in global configuration mode, as shown in the following example:

apic1(config)# tenant exampleCorp

Create a private network (also called VRF) in tenant configuration mode as shown in the following example:

apic1(config)# tenant exampleCorp
apic1(config-tenant)# vrf context exampleCorp_v1
apic1(config-tenant-vrf)# exit

Create a bridge domain (BD) under the tenant, as shown in the following example:

apic1(config-tenant)# bridge-domain exampleCorp_b1
apic1(config-tenant-bd)# vrf member exampleCorp_v1
apic1(config-tenant-bd)# exit

Allocate IP addresses for the BD (ip and ipv6), as shown in the following example.

apic1(config-tenant)# interface bridge-domain exampleCorp_b1
apic1(config-tenant-interface)# ip address 172.1.1.1/24
apic1(config-tenant-interface)# ipv6 address 2001:1:1::1/64
apic1(config-tenant-interface)# exit

Create an application profile, as shown in the following example ("exampleCorp_web1"):

apic1(config)# tenant exampleCorp
apic1(config-tenant)# application exampleCorp_web1

Create an EPG under the application, as shown in the following example ("exampleCorp_webepg1"):

apic1(config-tenant-app)# epg exampleCorp_webepg1
 

Associate the EPG to the bridge domain, shown as follows:

apic1(config-tenant-app-epg)# bridge-domain member exampleCorp_b1
apic1(config-tenant-app-epg)# exit
apic1(config-tenant-app)# exit
apic1(config-tenant)# exit

Create a dynamic or static VLAN pool.

apic1# config
apic1(config)# vlan-domain AVS-DOM2 dynamic                                                   

apic1# config
apic1(config)# vlan-domain AVS-DOM2

Define a dynamic or static allocation block.

apic1(config-vlan)# vlan 1071-1075 dynamic 
                                          

apic1(config-vlan)# vlan 1071-1075

Allocate dynamic or static encapsulation blocks.

apic1(config-vlan)# vlan 1076-1080,1091 dynamic
scale-apic1(config-vlan)#
apic1(config-vlan)# exit 

apic1(config-vlan)# vlan 1076-1080,1091
scale-apic1(config-vlan)#
apic1(config-vlan)# exit 

Associate the VLAN pool to the VMM domain.

apic1(config)# vmware-domain AVS-DOM2
apic1(config-vmware)# vlan-domain member AVS-DOM2         
apic1(config-vmware)# exit
apic1(config)# exit
apic1#  
apic1# show vlan-domain

To get into the configuration mode using the NX-OS CLI, enter the following:

apic1#configure
apic1(config)#

Create an application network profile for the tenant.

apic1(config)# tenant exampleCorp
apic1(config-tenant)# application OnlineStore   
apic1(config-tenant-app)# 

Create application web, db, and app EPGs for this application network profile of the tenant.

    
apic1(config-tenant-app)# epg web
apic1(config-tenant-app-epg)# exit
apic1(config-tenant-app)# epg db
apic1(config-tenant-app-epg)# exit
apic1(config-tenant-app)# epg app
apic1(config-tenant-app-epg)# exit

Get back into the tenant mode to create an access list (filter) for different traffic types between these EPGs.

apic1(config-tenant-app)# exit

Create an access list (filter) for the http and https traffic.

apic1(config-tenant)# access-list http
apic1(config-tenant-acl)# match tcp dest 80
apic1(config-tenant-acl)# match tcp dest 443
apic1(config-tenant-acl)# exit

Create an access list (filter) for Remote Method Invocation (RMI) traffic.

apic1(config-tenant)# access-list rmi
apic1(config-tenant-acl)# match tcp dest 1099
apic1(config-tenant-acl)# exit

Create an access list (filter) for the SQL/database traffic.

apic1(config-tenant)# access-list sql
apic1(config-tenant-acl)# match tcp dest 1521
apic1(config-tenant)# exit

Create the contracts and assign an access group (filters) for RMI traffic between EPGs.

apic1(config)# tenant exampleCorp
apic1(config-tenant)# contract rmi
apic1(config-tenant-contract)# subject rmi
apic1(config-tenant-contract-subj)# access-group rmi both
apic1(config-tenant-contract-subj)# exit
apic1(config-tenant-contract)# exit

Create the contracts and assign an access group (filters) for web traffic between EPGs.

 
apic1(config-tenant)# contract web
apic1(config-tenant-contract)# subject web
apic1(config-tenant-contract-subj)# access-group http both
apic1(config-tenant-contract-subj)# exit

Create the contracts and assign an access group (filters) for SQL traffic between EPGs.

apic1(config-tenant)# contract sql
apic1(config-tenant-contract)# subject sql
apic1(config-tenant-contract-subj)# access-group sql both
apic1(config-tenant-contract-subj)# exit
apic1(config-tenant-contract)# exit

Attach the bridge domain and contracts to the web EPG.

apic1(config-tenant)# application OnlineStore
apic1(config-tenant-app)# epg web
apic1(config-tenant-app-epg)# bridge-domain member exampleCorp_b1
apic1(config-tenant-app-epg)# contract consumer rmi
apic1(config-tenant-app-epg)# contract provider web
apic1(config-tenant-app-epg)# exit

Attach the bridge domain and contracts to the db EPG.

apic1(config-tenant-app)# epg db
apic1(config-tenant-app-epg)# bridge-domain member exampleCorp_b1
apic1(config-tenant-app-epg)# contract provider sql
apic1(config-tenant-app-epg)# exit

Attach the bridge domain and contracts to the application EPG.

apic1(config-tenant-app)# epg app
apic1(config-tenant-app-epg)# bridge-domain member exampleCorp_b1

Associate the provider contracts to the application EPGs.

apic1(config-tenant-app-epg)# contract provider rm1
apic1(config-tenant-app-epg)# contract consumer sql
apic1(config-tenant-app-epg)# exit
apic1(config-tenant-app)# exit
apic1(config-tenant)# exit

Associate the ports and VLANs to the EPGs app, db, and web.

apic1(config)# leaf 103
apic1(config-leaf)# interface ethernet 1/2-4
apic1(config-leaf-if)# vlan-domain member exampleCorp
apic1(config-leaf)# exit
apic1(config)# leaf 103
apic1(config-leaf)# interface ethernet 1/2
apic1(config-leaf-if)# switchport
access  trunk  vlan
apic1(config-leaf-if)#  switchport trunk allowed vlan 100 tenant exampleCorp application OnlineStore epg app
apic1(config-leaf-if)# exit
apic1(config-leaf)# interface ethernet 1/3
apic1(config-leaf-if)#  switchport trunk allowed vlan 101 tenant exampleCorp application OnlineStore epg db
apic1(config-leaf-if)# exit
apic1(config-leaf)# interface ethernet 1/4
apic1(config-leaf-if)#  switchport trunk allowed vlan 102 tenant exampleCorp application OnlineStore epg web
apic1(config-leaf-if)# exit

Log in to the Cisco APIC.

On the menu bar, choose TENANTS and the tenant in which you created the application profile and EPGs.

In the navigation pane, expand the tenant folder and then expand the Application Profiles folder.

Verify that the application profile that you created appears.

Open the application profile folder and then click the Application EPGs folder.

In the work pane, verify that the EPGs that you created appear and then click each EPG to view its properties.

Log in to the vCenter.

Navigate to the Cisco AVS.

Verify that the EPGs that you created appear among the port groups for the Cisco AVS.

Log in to the vCenter.

Navigate to one of the virtual machines VMs that you want to test.

Click the console tab for the VM.

Log in to the VM.

Access the command prompt and enter the following command:ping Second IP address

View the results to ensure that the two VMs can communicate.

Repeat Step 2 through Step 6 as needed.

Log in to the VMware vSphere Client.

Choose Home > Inventory > Hosts and Clusters.

In the navigation pane, click the server with the VM and then click the VM.

In the central pane, click Edit virtual machine settings.

In the Virtual Machine Properties dialog box, make sure that the Hardware tab is chosen.

In the navigation pane, click the network adapter.

In the Network Label area, choose a port group and then click OK.

Log into the VM.

Use the command appropriate for your environment (such as ifconfig for Linux and ipconfig for Windows) to list the IP addresses assigned to the network adapter.

Use the configuration procedure relevant to your version of Linux or Windows to assign a new persistent (static or dynamic) IPv4 or IPv6 address within the desired subnet of the EPG or bridge domain.

Log out of the VM.

Log in to Cisco APIC.

Complete one of the following sets of steps:

• If you are configuring a gateway under the bridge domain subnets, complete Step 3 through Step 7 and skip Step 8 through 12.
• If you are configuring a gateway under the EPG subnets, skip Step 3 through Step 7 and complete Step 8 through Step 12.

Choose Tenants > tenant_name > Networking > Bridge Domains > bridge_domain_name > Subnets.

On the right side of the work pane, click the + icon.

In the Create Subnet dialog box, in the Gateway IP field, enter the gateway IPv4 or IPv6 address.

Accept the default values in the dialog box.

Click SUBMIT.

Choose Tenant > tenant_name > Application Profiles > application_profile_name > Application EPGs > epg_name > Subnets.

On the right side of the work pane, click the ACTIONS down arrow and choose Create EPG Subnet.

In the Create EPG Subnet dialog box, in the Default Gateway IP field, enter the gateway IPv4 or IPv6 address.

Accept the default values in the dialog box.

Click SUBMIT.

Choose Virtual Networking > Inventory > VMM Domains > VMware > VMM_name > Controllers > data center_name > DVS-VMM name > Portgroups > EPG_name > Learned Point MAC address (Node).

Click the Stats tab.

Click the tab with the check mark.

In the Select Stats dialog box, click the statistics that you want to view in the Available pane and then click the arrow pointing right to put them in the Selected pane.

(Optional) Choose a sampling interval different from the default of 5 minutes.

Click SUBMIT.

Choose Virtual Networking > Inventory > VMM Domains > VMware > VMM_name > Controllers > data center_name > DVS-VMM name > Portgroups > EPG_name > Learned Point MAC address (Node)

Click the Stats tab.