Forwarding Scale Profile Configuration

Configuring Forwarding Scale Profiles Using GUI

The forwarding scale profile policy provides different scalability options. For more information on the scalability options, see the Forwarding Scale Profile Policy Overview section in the chapter for your Cisco Application Policy Infrastructure Controller (APIC) release.

This section explains how to configure forwarding scale profiles using the Cisco APIC GUI.

Before you begin

  • Read through and follow the Guidelines and Limitations section.

  • Ensure you have access to the Cisco APIC GUI.

  • Ensure that your switches support the profile you want to configure. For the list of supported switches, see the release-specific chapter.

  • Changing the scale profile for individual members of a vPC is not allowed. If members of the same vPC are associated with different leaf profiles, then a new leaf profile should be created with both members and the scale profile applied to it.

Procedure

Step 1

To create the policy, perform the following steps:

  1. From the top navigation menu, choose Fabric > Access Policies.

  2. In the left navigation pane, expand Policies > Switch.

  3. Right-click Forwarding Scale Profile and choose Create Forwarding Scale Profile Policy.

  4. In the Create Forwarding Scale Profile Policy dialog, provide a Name, optional Description, and the Type for the policy.

  5. Click Submit.

Step 2

To add the policy to a policy group to enable it to be associated with fabric nodes, perform the following steps:

  1. From the top navigation menu, choose Fabric > Access Policies.

  2. In the left navigation pane, expand Switches > Leaf Switches.

  3. Right-click Policy Groups and choose Create Access Switch Policy Group

  4. From the Create Access Switch Policy Group dialog, click the Forward Scale Profile Policy drop-down arrow and choose the policy you previously configured.

  5. Click Submit.

Step 3

To associate the policy group to a node, perform the following steps:

  1. From the top navigation menu, choose Fabric > Access Policies.

  2. In the left navigation pane, expand Switches > Leaf Switches.

  3. Right-click Profiles and choose Create Leaf Profile.

  4. Enter a name for the profile in the Name field.

  5. From the Leaf Selectors table, click the + icon to access the Leaf Selectors table fields.

  6. Enter a name in the Name field.

  7. Choose one or more switches to associate the the profile from the Blocks drop-down list.

  8. Chose the policy group containing your Forwarding Scale Profile Policy from the Policy Group drop-down list.

  9. Click Update.

  10. Click Next.

  11. Click Finish.

Step 4

Manually reload the switch after the forwarding scale profile policy is applied for the changes to take effect.

Configuring Forwarding Scale Profiles Using CLI

The Forwarding Scale Profile policy provides different scalability options. For more information on the scalability options, see the Forwarding Scale Profile Policy Overview section in the chapter for your Cisco APIC release.

This section explains how to configure forwarding scale profiles using the CLI.

Before you begin

  • Read through and follow the Guidelines and Limitations section.

  • Ensure you have access to the switch via CLI

  • Ensure that your switches support the profile you want to configure. For the list of supported switches, see the release-specific section.

  • Changing the scale profile for individual members of a VPC is not allowed. If members of the same VPC are associated with different leaf profiles, then a new leaf profile should be created with both members and the scale profile applied to it.

Procedure

Step 1

Enter global configuration mode 

apic1# configure

Step 2

Define the scale-profile policy 

apic1(config)# scale-profile <scale-profile-name>

Step 3

Set the Forwarding Scale profile type.

You can use the profile-type {dual-stack | high-dual-stack | high-lpm | high-policy | ipv4 } command to set the type: 

apic1(config-scale-profile)# profile-type ipv4

Step 4

Return back to global configuration. 

apic1(config-scale-profile)# exit

Step 5

Define the leaf policy group.

apic1(config)# template leaf-policy-group <leaf-policy-group-name>

Step 6

Configure the relation between the scale profile policy and the leaf policy group.

apic1(config-leaf-policy-group)# scale-profile <scale-profile-name>

Note

 

The switches that support the forwarding scale profile policy must be manually reloaded after the forwarding scale profile policy is applied. For a list of supported switches, see the Supported Platforms for Forwarding Scale Profile Policies section in the chapter for your Cisco APIC release.

Step 7

Return back to global configuration. 

apic1(config-leaf-policy-group)# exit

Step 8

Configure a leaf profile.

apic1(config)# leaf-profile <leaf-profile-name>

Step 9

Specify a group of leaf switches.

apic1(config-leaf-profile)# leaf-group <leaf-group>

Step 10

Add leaf switches to the leaf group.

apic1(config-leaf-profile)# leaf 201

Step 11

Specify the leaf policy group to be associated to the leaf switches

apic1(config-leaf-group)# leaf-policy-group <leaf-policy-group-name>

Step 12

Exit command mode. 

apic1(config-leaf-policy-group)# exit

Step 13

(Optional) Display the current running configuration.

apic1(config)# show running-config
# Command: show running-config scale-profile testFwdScaleProf
# Time: Thu Jul 27 22:31:29 2017
  scale-profile testFwdScaleProf
    profile-type ipv4
    exit
apic1(config-leaf-group)# show running-config leaf-profile sampleLeafProf
# Command: show running-config leaf-profile sampleLeafProf
# Time: Tue Aug  1 11:19:58 2017
  leaf-profile sampleLeafProf
    leaf-group sampleLeafGrp
      leaf 201
      leaf-policy-group samplePolicyGrp
      exit

Step 14

Manually reload the switch after the forwarding scale profile policy is applied for the changes to take effect.
This example shows how to configure the IPv4 scale profile policy.

apic1# configure
apic1(config)# scale-profile testFwdScaleProf
apic1(config-scale-profile)# profile-type ipv4
apic1(config-scale-profile)# exit
apic1(config)# template leaf-policy-group samplePolicyGrp
apic1(config-leaf-policy-group)# scale-profile testFwdScaleProf
apic1(config-leaf-policy-group)# exit
apic1(config)# leaf-profile sampleLeafProf
apic1(config-leaf-profile)# leaf-group sampleLeafGrp
apic1(config-leaf-profile)# leaf 201
apic1(config-leaf-group)# leaf-policy-group samplePolicyGrp
apic1(config-leaf-group)# show running-config scale-profile testFwdScaleProf 
# Command: show running-config scale-profile testFwdScaleProf
# Time: Thu Jul 27 22:31:29 2017
  scale-profile testFwdScaleProf
    profile-type ipv4
    exit
apic1(config-leaf-group)# show running-config template leaf-policy-group samplePolicyGrp
# Command: show running-config template leaf-policy-group samplePolicyGrp
# Time: Tue Aug  1 11:19:44 2017
  template leaf-policy-group samplePolicyGrp
    scale-profile testFwdScaleProf
    exit
apic1(config-leaf-group)# show running-config leaf-profile sampleLeafProf
# Command: show running-config leaf-profile sampleLeafProf
# Time: Tue Aug  1 11:19:58 2017
  leaf-profile sampleLeafProf
    leaf-group sampleLeafGrp
      leaf 201
      leaf-policy-group samplePolicyGrp
      exit

Configuring Forwarding Scale Profiles Using REST API

The Forwarding Scale Profile policy provides different scalability options. For more information on the scalability options, see the Forwarding Scale Profile Policy Overview section in the chapter for your Cisco APIC release.

This section explains how to configure forwarding scale profiles using REST API.

Before you begin

  • Read through and follow the Guidelines and Limitations section.

  • Ensure that your switches support the profile you want to configure. For the list of supported switches, see the release-specific section.

  • Changing the scale profile for individual members of a VPC is not allowed. If members of the same VPC are associated with different leaf profiles, then a new leaf profile should be created with both members and the scale profile applied to it.

Procedure

Step 1

To apply a forwarding scale profile policy with IPv4 scaling, send a post with XML similar to the following example:

<polUni>
    <infraInfra>
        <topoctrlFwdScaleProfilePol name=“sampleFwdScaleProf" profType="ipv4"/>
        <infraAccNodePGrp name=“sampleNodePolGrp">
            <infraRsTopoctrlFwdScaleProfPol tnTopoctrlFwdScaleProfilePolName=“sampleFwdScaleProf"/>
        </infraAccNodePGrp>
        <infraNodeP name=“nodeProf_101">
            <infraLeafS name=“leafS_101" type="range">
                <infraNodeBlk name="test" from_="101" to_="101"/>
                <infraRsAccNodePGrp tDn="uni/infra/funcprof/accnodepgrp-sampleNodePolGrp "/>
            </infraLeafS>
        </infraNodeP>
    </infraInfra>
</polUni>

Step 2

Manually reload the switch after the forwarding scale profile policy is applied for the changes to take effect.

Verifying Forwarding Scale Profiles on the Switch

This section provides a few commands you can use to verify the forwarding scale profile configuration on your switch.

  • Displaying forwarding scale profiles supported on a switch.

    switch# cd /mit/sys/configProfile
switch# dir
cfgent-default   cfgent-high-dual-stack   cfgent-high-lpm   cfgent-high-policy   cfgent-ipv4   summary

  • Displaying the current forwarding scale profile on a switch.

    In the following command,

    • currentProfile, indicates the forwarding scale profile that is currently running on the switch.

      Note that this field is available starting with Release 4.1(1). In prior releases, you can verify the currently running scale profile only by checking the scale values in the capacity dashboard of the APIC GUI.

    • profType indicates the forwarding scale profile that you configured for the switch. 

    switch# moquery -c topoctrlFwdScaleProf 
# topoctrl.FwdScaleProf
annotation     : 
childAction    : 
currentProfile : sys/configProfile/cfgent-ipv4
dn             : sys/topoctrl/fwdprofile
extMngdBy      : 
lcOwn          : local
modTs          : 2019-08-21T13:03:18.185-07:00
profType       : ipv4
rn             : fwdprofile
status         : 
uid            : 0

  • Display the policy (actrlRule) scale on the switch: 

    switch# moquery -c actrlRule -x rsp-subtree-include=count | grep count
count : 255000