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	Max. no. of static LAGs: 32 Max. no. of ports in single static LAG: 64 Max. no. of LACP LAGs: 32 Max. no. of ports in single LACP LAG: 64
Tunnel Termination	Only transport tunnel (GRE/ERSPAN)	1000	dest vtep: 1000 Inner SAP TCAM: 2000
	Outer VXLAN header (only)	1000
	Outer MPLS header (only)	1000
	Transport tunnel + Outer VXLAN header + Outer MPLS header	1000
Non-Transport Tunnel	NA	2000
Ingress Group	Physical ports and port channels	256	The no. of ingress groups on physical port or port channel depends on the physical ports.
	Transport tunnels only	1000	dest vtep: 1000 Inner SAP: 2000 Limit: 1000
	Non-transport tunnels only	2000	Max. inner SAP: 2000 TCAM: Max. 1000 entries for overlapping or shared entries across features
Route-map or route-map instances	NA	4000	The no. of route-map entries in the hardware and limit depends on ACL rules. No. of ACLs: 9500 No. of route-maps: 10000 No. of ingress groups: 2000 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 8000 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 the 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	NA	128	Max. length range match: 128
Egress Group	NA	128 (no replication) 126 (replication)	Max. no. of unique egress objects + max. no. of egress-groups with replication cannot exceed 128. If replication is not enabled, egress group acts as a container and does not consume anything from the hardware. Replication requires at least two egress groups or objects. If replication is enabled, egress group consumes one SFC entry for each group. Examples: Max. no. of egress groups or objects (with two same egress objects across all egress-groups): 126 Max. no. of egress groups or objects (with unique egress object per egress-group): 42
Egress	NA	128	Egress objects limit depends on the SFC table which supports 128 entries. Egress groups (with replication enabled) use the SFC table. If replication is not configured, the max. no. of egress objects allowed is 128.
Egress ACL	MAC	512	If the ACL is attached to a listener policy which is attached to an egress object, the entries are programmed to the 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	512
	Pv6	512
Egress Range support IP packet length Source L4 port Destination L4 port L4 port range	NA	128	The max. length range match is 128 ACL rules.
Listener Policy	NA	484	The no. of listener policy entries in the hardware and limit depends on ACL rules. Egress ACLs: 484 The listener policy is attached to egress objects. Each listener policy can have three instances. Max. no. of egress objects: 128.
Tunnel Origination	NA	128	The hardware supports 512 tunnel origination which is attached to egress objects. Egress objects limit: 128
Onboard PCAP Sessions	NA	10
VXLAN/MPLS Mirrors	NA	250	When configured, a copy of the full untagged VXLAN or MPLS frame is mirrored to the configured egress port without any header termination. Max. no. of VXLAN mirrors + max. no. MPLS mirrors: 250