New and Changed Information

The following table provides an overview of the significant changes to this guide up to this current release. The table does not provide an exhaustive list of all changes made to the guide or of the new features up to this release.

Table 1. New Features and Changed Behavior

Cisco APIC Release Version

Feature

Description

Release 4.0(1)

Updated High Dual Stack numbers for Multicast.

The High Dual Stack numbers for Multicast changed for Cisco APIC Release 4.0(1).

Release 3.2(1)

High LPM scaling option and updated profile scaling numbers.

New option providing scalabilty similar to the dual-stack policy, except that the longest prefix match (LPM) scale is 128,000 and the policy scale is 8,000.

Release 3.1(1)

High Dual Stack

The high dual stack option is added to provide the scalability specified in the Forwarding Scale Profile Policy Overview.

Release 3.0(1)

IPv4 scale profile

The IPv4 scale profile policy was added.

Supported Platforms for Forwarding Scale Profile Policies

The forwarding scale profile policy is only supported on the following switches:

  • Cisco Nexus 9300-EX Series switches

  • Cisco Nexus 9300-FX Series switches

  • Cisco Nexus 9300-FX2 Series switches

The Cisco Nexus 9358GY-FXP switch does not support the forwarding scale profiles.

Forwarding Scale Profile Policy Overview

The Forwarding Scale Profile policy provides different scalability options. For example:

  • Dual Stack—Provides scalability of up to 12,000 endpoints for IPv6 configurations and up to 24,000 endpoints for IPv4 configurations.

  • High LPM—Provides scalability similar to the dual-stack profile, except that the longest prefix match (LPM) scale is 128,000 and the policy scale is 8,000.

  • IPv4 Scale—Enables systems with no IPv6 configurations to increase scalability to 48,000 IPv4 endpoints.

  • High Dual Stack—Provides scalability of up to 64,000 MAC endpoints and 64,000 IPv4 endpoints. IPv6 endpoint scale can be 24,000/48,000, depending on the switch hardware model.


    Note

    The Cisco Nexus 9358GY-FXP switch does not support the forwarding scale profiles. The information in this document is therefore not applicable for this switch.



    Note

    With Cisco APIC Release 3.2(1), depending on your TOR switch hardware, a Forwarding Scale Profile with the High Dual Stack option has different scales; for example:

    • For Cisco Nexus 9000 Series TOR switches with FX in the switch name (except FX2), the high dual-stack option has scalability of 48,000 IPv6 endpoints instead of 24,000 and 128,000 policies instead of 8,000.

    • For Cisco Nexus 9000 Series TOR switches with FX2 in the switch name, the scale values are same as those of EX Series switches.

    • For Cisco Nexus 9000 Series TOR switches with EX in the switch name, the high dual-stack option has the same EP scale values as with earlier APIC releases.


See the following table for more details.

Forwarding Scale Profile Policy Scalability for Cisco APIC Release 4.1(1)

Forwarding Scale Profile Policy Options

TOR Switches with EX and FX2 Names

TOR Switches with FX Names

Dual Stack

  • EP MAC: 24,000

  • EP IPv4: 24,000

  • EP IPv6: 12,000

  • LPM: 20,000

  • Policy: 64,000

  • Multicast: 8,000

Has the same scalability numbers as Dual Stack scale on earlier switches.

High Dual Stack

  • EP MAC: 64,000

  • EP IPv4: 64,000

  • EP IPv6: 24,000

  • LPM: 38,000

  • Policy: 8,000

  • Multicast: 512

  • EP MAC: 64,000

  • EP IPv4: 64,000

  • EP IPv6: 48,000

  • LPM: 38,000

  • Policy: 128,000

  • Multicast: 32,000

High LPM

Provides scalability similar to the dual-stack profile, except that the longest prefix match (LPM) scale is 128,000 and the policy scale is 8,000.

Has the same scalability numbers as on earlier switches.

IPv4 Scale

  • EP MAC: 48,000

  • EP IPv4: 48,000

  • EP IPv6: 0

  • LPM: 38,000

  • Policy: 64,000

  • Multicast: 8,000

Has the same scalability numbers as IPv4 scale on earlier switches.


Note

  • Because the IPv4 forwarding scale profile policy does not support IPv6 configurations, all IPv6 configurations must be removed from switches that are configured with the IPv4 forwarding scale profile policy.

  • For ToR switch models with EX at the end of the switch name, because the high dual stack profile has reduced-scale support for contract policies (8,000), the contracts scale must be reduced accordingly before deploying that profile.

  • Before migrating to minimal tenant multicast scale leaf profiles, such as high dual stack, we recommend that you first disable Layer 2 IGMP snooping-, Layer 3 IGMP-, and PIM-related configurations to prevent having a stale multicast state in your hardware.

  • Applying a scale profile to a node requires a manual reload of that node. Any unsupported switches are ignored. For a list of supported switches, see Supported Platforms for Forwarding Scale Profile Policies.

  • VPCs associated with different scale profile settings are not supported. The VPC members must be configured with the same scale profile settings.



Note

In Cisco APIC Release 4.1(1), the policy count updates that are reported by the leaf switches to the Cisco APIC through the MO actrlRuleHit5min is set to 0 for the High Dual Stack profile for all platforms.



Note

With the default deny model in Cisco ACI, the configured tenant or VRFs have implicit rules that consume several TCAM entries for each VRF. With an increase in the number of VRFs configured on a single switch, these TCAM entries that are used per VRF also count toward the overall policy TCAM usage.


Configuring the Forwarding Scale Profile Policy Using the Cisco APIC GUI

The Forwarding Scale Profile policy provides different scalability options. For more information on the scalability options, see Forwarding Scale Profile Policy Overview.

Before you begin

  • Access to the APIC GUI

  • The forwarding scale profile policy requires supported switches. For a list of supported switches, see Supported Platforms for Forwarding Scale Profile Policies.


    Note

    • The switches that support forwarding scale profile policies must be manually reloaded after the forwarding scale profile policy is applied.

    • 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. Click Fabric > External Access Policies.

  2. From the Navigation pane, expand Policies and Switch.

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

  4. In the Create Forwarding Scale Profile Policy dialog, enter a name for the policy in the Name field and choose the type.

  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. Click Fabric > External Access Policies.

  2. Expand Switches and 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. Click Fabric > External Access Policies.

  2. Expand Switches and 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.


What to do next

To enable the forwarding scale profile policy, you must manually reload the switches that are to consume it.

Configuring the Forwarding Scale Profile Policy Using the NX-OS-Style CLI

Before you begin

The Forwarding Scale Profile policy provides different scalability options. For more information on the scalability options, see Forwarding Scale Profile Policy Overview.

The forwarding scale profile policy requires supported switches. For a list of supported switches, see Supported Platforms for Forwarding Scale Profile Policies.


Note

  • The switches that support the forwarding scale profile policy must be manually reloaded after the forwarding scale profile policy is applied.

  • 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.


This section demonstrates how to configure the forwarding scale profile policy using the NX-OS-style CLI.

Procedure

  Command or Action Purpose
Step 1

configure

Example:

apic1# configure

Enters global configuration mode.

Step 2

no scale-profile name

Example:

apic1(config)# scale-profile testFwdScaleProf

Defines the scale-profile policy.

Step 3

profile-type {dual-stack | high-dual-stack | high-lpm | ipv4 }

Example:

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

Sets the Forwarding Scale profile type.

Step 4

exit

Example:

apic1(config-scale-profile)# exit

Returns back to global configuration.

Step 5

template leaf-policy-group leaf_group_name

Example:

apic1(config)# template leaf-policy-group samplePolicyGrp

Defines the leaf policy group.

Step 6

scale-profile name

Example:

apic1(config-leaf-policy-group)# scale-profile testFwdScaleProf

Configures the relation between the scale-profile policy and the leaf policy group.

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 switches that support the forwarding scale profile policy, see Supported Platforms for Forwarding Scale Profile Policies.

Step 7

exit

Example:

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

Returns back to global configuration.

Step 8

leaf-profile leaf_profile_name

Example:

apic1(config)# leaf-profile sampleLeafProf

Configures a leaf profile.

Step 9

leaf-group leaf_group_name

Example:

apic1(config-leaf-profile)# leaf-group sampleLeafGrp

Specifies a group of leaf switches.

Step 10

leaf leaf_group_number

Example:

apic1(config-leaf-profile)# leaf 201

Adds leaf switches to the leaf group.

Step 11

leaf-policy-group leaf_policy_group_name

Example:

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

Specifies the leaf policy group to be associated to the leaf switches.

Step 12

exit

Example:

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

Exits command mode.

Step 13

[show] running-config

Example:


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-scale-profile)#

Displays the current running configuration.

Step 14

[show] template leaf-policy-group

Example:


Displays the current running configuration.

Examples

This example shows how to configure a 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 the Forwarding Scale Profile Policy Using the REST API

The forwarding scale profile policy requires supported switches. For a list of supported switches, see Supported Platforms for Forwarding Scale Profile Policies. The switches that support the forwarding scale profile policy must be manually reloaded after the forwarding scale profile policy is applied.

The Forwarding Scale Profile policy provides different scalability options. For more information on the scalability options, see Forwarding Scale Profile Policy Overview.

This section explains how to create a forwarding scale profile policy and apply it to a leaf profile using the REST API.

Procedure


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

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>

To take effect, the switches that support the forwarding scale profile policy must be manually reloaded after the forwarding scale profile policy is applied.