Forwarding Scale Switch Policy
Location in GUI: Fabric
» Access Policies
» Policies
» Switch
» Forwarding Scale Profiles
Diagram
Section titled “Diagram”Classes
Section titled “Classes”switch_policies (apic.access_policies)
Section titled “switch_policies (apic.access_policies)”Name | Type | Constraint | Mandatory | Default Value |
---|---|---|---|---|
forwarding_scale_policies | List | [forwarding_scale_policies] | No |
forwarding_scale_policies (apic.access_policies.switch_policies)
Section titled “forwarding_scale_policies (apic.access_policies.switch_policies)”Name | Type | Constraint | Mandatory | Default Value |
---|---|---|---|---|
name | String | Regex: ^[a-zA-Z0-9_.:-]{1,64}$ | Yes | |
profile | Choice | dual-stack , ipv4 , high-dual-stack , high-lpm , high-policy , high-ipv4-ep , mcast-heavy , max-lpm | No | dual-stack |
Examples
Section titled “Examples”Example-1: this example configures a HIGH-DUAL-STACK
forwarding scale policy, which chooses the profile type of high-dual-stack
, which increaes the IPv4 and IPv6 routing scale in favor of other scaling options such as TCAM for contracts, EP table, or multicast routing. The exact nature of the profile to choose will be based on the switch model, published scaling numbers for each profile, and the leaf switch role within the fabric (e.g. border, compute, service, or mixed leaf).
apic: access_policies: switch_policies: forwarding_scale_policies: - name: HIGH-DUAL-STACK profile: high-dual-stack