Scalability Matrix

The following table summarizes scale limitations for the NPB application forwarding features.

Table 1. Scalability matrix
Feature Sub-Group Product Scale Description
Port Channel NA 32
  • No. of ports in a LAG: 64
  • LAG members: 2048
  • LAG groups: 32 (with 64 members each LAG group)
Transport Tunnel (only IPv4) NA 256
  • dest vtep: 1000
  • n/w SAP: 8000
  • Inner SAP TCAM: 256
Non-Transport Tunnel NA 2000
Ingress Group Physical ports and port channels 256
  • No. of ingress groups on physical port or port channel depends on physical ports.
  • Limit: 256
Transport tunnels only 256
  • dest vtep: 1000
  • n/w SAP: 8000
  • Inner SAP: 256
  • Limit: 256
Non-transport tunnels only 2000
  • Max inner SAP: 2000 ( with exact match RAM)
  • TCAM: Max 256 entries for overlapping or shared entries across features
Route map or route map instances NA 4000
  • No route map entries in hardware and limit depends on ACL rules
  • No. of ACLs: 9500
  • No. of route-maps: 10K
  • No. of ingress groups: 2K

The route-maps are attached to ingress groups. Each route-map can have only one ingress group instance and each instance can have only one ACL. So only 8K route-maps are supported.

Ingress ACL MAC 1500
  • If the ACL is attached to a route map which is attached to an ingress group, the entries are programmed to hardware (TCAM).
  • If an ACL contains x no. of rule entries that are attached to y no. of route maps, then x * y denotes the consumed TCAM space.
IPv4 6000
IPv6 2000
Ingress Range support:
  • IP packet length
  • Source L4 port
  • Destination L4 port
  • L4 port range
128 Maximum length range match: 128.
Egress Group NA
  • 128 (no replication)
  • 126 (replication)
  • If replication is not enabled, egress group acts as a container and does not consume anything from hardware.
  • Replication requires at least two egress groups/objects.
  • If replication is enabled, egress group consumes one SFC entry for each group.

Max. no. of unique egress objects + max. no. of egress-groups with replication cannot exceed 128.

Examples:

  • Max. no. of egress group/object (with two same egress objects across all egress-groups): 126.
  • max no. of egress group/object (with unique egress object per egress-group): 42

Egress NA 128
  • Egress objects limit depends on the SFC table which supports 128 entries.
  • The SFC table is used by egress group with replication enabled.
  • If replication is not configured, the maximum no. of egress objects allowed is 128.
Egress ACL MAC 128
  • If the ACL is attached to a listener policy which is attached to an egress object, the entries are programmed to hardware (TCAM).
  • If an ACL contains x no. of rule entries that are attached to y no. of listener policies, then x * y denotes the consumed TCAM space.
IPv4 128
Pv6 128
Egress Range support
  • IP packet length
  • Source L4 port
  • Destination L4 port
  • L4 port range
128 The maximum length range match is 128 ACL rules.
Listener Policy NA 128
  • No listener policy entries in hardware and limit depends on ACL rules.
  • Egress ACLs: 384

Each listener policy can have only one instance and each instance can have only one ACL and each ACL can have only one rule. The listener policy is attached to egress objects and the maximum no. of egress objects supported is 128.

Tunnel Origination NA 128
  • Hardware supports 512 tunnel origination which is attached to egress objects.
  • Egress objects limit: 128
Onboard PCAP Sessions NA 10 Limited to 10 as AHA requirement is 10.