Verified Scalability Limits

Introduction

Verified Scalability Limits (Unidimensional)

Verified Scalability Limits

This chapter describes the Cisco NX-OS configuration limits for the Cisco Nexus 31128PQ switch.

- Introduction

- Verified Scalability Limits (Unidimensional)

Introduction

The values provided in this guide should not be interpreted as theoretical system limits for Cisco Nexus 31128PQ hardware or Cisco NX-OS software. These limits refer to values that have been validated by Cisco. They can increase over time as more testing and validation is done.

Verified Scalability Limits (Unidimensional)

The tables in this section list the unidimensional verified scalability limits for Cisco NX-OS Release 7.0(3)I5(1) on the Cisco Nexus 31128PQ switch. The values provided in these tables focus on the scalability of one particular feature at a time.

Each number is the absolute maximum currently supported by this Cisco NX-OS release for the corresponding feature. If the hardware is capable of a higher scale, future software releases might increase this verified maximum limit. Results might differ from the values listed here when trying to achieve maximum scalability with multiple features enabled.

Interfaces Verified Scalability Limits (Unidimensional)

Feature

31128PQ Verified Limit

DHCP clients per switch

10 (IPv4) + 10 (IPv6)

BFD sessions

128 (IPv4) + 128 (IPv6)

Generic routing encapsulation (GRE) tunnels

8

Port channel links

32

SVIs

250

vPCs

60

Label Switching Verified Scalability Limits (Unidimensional)

Feature

31128PQ Verified Limit

Forwarding Equivalence Classes (FECs)

128

Equal-cost multipaths (ECMPs)

16

FECs * ECMPs

1000

Flex counters for static MPLS in egress direction

4000

Flex counters per adjacency

2

Adjacencies

1024

Egress Per Engineering

64

Note

The maximum number of FECs and ECMPs cannot be configured at the same time. For example, if you have 128 FECs and all of those FECs have 8 ECMPs, you will have 128 * 8 = 1024 adjacencies, so egress statistics will be supported for all. In contrast, if you have 100 FECs and all of those FECs have 16 ECMPs, you will have 100 * 16 = 1600 adjacencies. Because a maximum of 1024 adjacencies are supported, the statistics might not work as expected.

Layer 2 Switching Verified Scalability Limits (Unidimensional)

Feature

31128PQ Verified Limit

MST instances

64

MST virtual ports

48,000

RPVST virtual ports

12,000

VLANs

3900

VLANs in RPVST mode

500

Total number of VLANs × ports with switchport isolated (3967 VLANs x 48 ports)

190,000

Note

The number of supported VLANs per vPC should be within the MST or RPVST virtual port count specified in this table, depending on the topology.

Multicast Routing Verified Scalability Limits (Unidimensional)

Feature

31128PQ Verified Limit

IPv4 multicast routes

8000 (Layer 2 + Layer 3)

Outgoing interfaces (OIFs)

40 (SVI + physical Layer 3)

IGMP snooping groups

8000

PIM neighbors

250

Note

The IPv4 multicast routes and the IPv4/IPv6 host routes share the same hardware table. Limits are provided for both the default line card mode and the max host line card mode.

Note

High availability (graceful restart and stateful switchover) is not supported when unicast or multicast aggressive timers are configured at any scale.

Security Verified Scalability Limits (Unidimensional)

Feature

31128PQ Verified Limit

DHCP snooping bindings

2048

IPv4 ingress ACLs

3070 (per network forwarding engine)

IPv4 egress ACLs

765 (per network forwarding engine)

IPv6 ingress ACLs

1530 (per network forwarding engine)

IPv6 egress ACLs

250 (per network forwarding engine)

Note

The ACL scalability limits also apply to policy-based ACLs (PBACLs).

System Management Verified Scalability Limits (Unidimensional)

Feature

31128PQ Verified Limit

MPLS Stripping

Labels

12,000

PTP

10G physical ports enabled for PTP

44

sFlow

sFlow ports

64

SPAN and ERSPAN

Configurable SPAN or ERSPAN sessions

32

Active SPAN or ERSPAN sessions[1]

4

Active localized SPAN or ERSPAN sessions per line card[2]

4

Source interfaces per SPAN or ERSPAN session (Rx and Tx, Rx, or Tx)

48

Destination interfaces per SPAN session

1 (physical interface)

Source VLANs per SPAN or ERSPAN session

32

TAP Aggregation

Redirect interfaces in the redirect port list

12

Redirect port lists (or fan outs) per system

100

[1] A single forwarding engine instance supports four SPAN or ERSPAN sessions. If the first three sessions have bidirectional sources, the fourth session might have hardware resources only for Rx sources, depending on the SPAN or ERSPAN source's forwarding engine instance mappings.

[2] The number of SPAN or ERSPAN sessions per line card reduces to two if the same interface is configured as the bidirectional source in more than one session.

Unicast Routing Verified Scalability Limits (Unidimensional)

Feature

31128PQ Verified Limit

Unicast Routing

BGP neighbors

512 (IPv4 only)

512 (IPv6 only)

256 (IPv4) + 256 (IPv6)

EIGRP neighbors

128 (IPv4), 128 (IPv6)

EIGRP routes

20,000

HSRP groups

250

IPv4 ARP

48,000

IPv4 host routes

208,000

IPv6 host routes

40,000

IPv6 ND

40,000

IPv4 unicast routes (LPM)

128,000

IPv6 unicast routes (LPM)

20,000

MAC addresses

80,000

OSPFv2 neighbors

256

OSPFv3 neighbors

256

VRFs

1000

VRRP groups per interface or I/O module

250

Policy-Based Routing (PBR)

Configured sequences per policy

256

Next-hop addresses per policy

32

IPv4 ACEs (unidimensional)

3072 (per network forwarding engine)

IPv6 ACEs (unidimensional)

1536 (per network forwarding engine)

IPv4 and IPv6s ACEs

2048 IPv4 + 256 IPv6

Interfaces with PBR policy

512

VRRPv3

VRRPv3 groups per interface

255

VRRPv3 groups with default timers

490

Pathways with one VRRPv3 group with default timer

489

VRRPv3 groups and pathways combined

490

Note

The IPv4 and IPv6 unicast routes share the same hardware table. Limits are provided for both the default line card mode and the max host line card mode.

Note

The IPv4/IPv6 host routes and the IPv4 multicast routes share the same hardware table. Limits are provided for both the default line card mode and the max host line card mode.

Note

High availability (graceful restart and stateful switchover) is not supported when unicast or multicast aggressive timers are configured at any scale.

Guidelines and Limitations for OSPF Verified Scalability Limits

- To achieve the highest scale, we recommend that you use a single OSPF instance instead of multiple instances.

- Each OSPFv2 and OSPFv3 scale value might vary when combined with other parameters.

- The graceful restart timeout value might need to be increased in multidimensional scenarios.

VXLAN Verified Scalability Limits (Unidimensional)

Feature

31128PQ Verified Limit

VXLAN Flood and Learn

Virtual network identifiers (VNIs) or VXLAN-mapped VLANs

1000

Underlay multicast groups

128

Overlay MAC addresses

64,000

Remote VXLAN tunnel endpoints (VTEPs)

256

Ingress replication peers

256

Ingress replication Layer 2 VNIs

1000

MAC addresses for ingress replication

64,000

VXLAN VLAN logical port VP count

6000

VXLAN BGP eVPN

Layer 2 VNI

1000

Underlay multicast groups

128

VTEPs

256

BGP VTEP peers

256

MAC addresses

64,000

VXLAN VLAN logical port VP count

6000

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. ( Click Here )

This product includes software written by Tim Hudson (tjh@cryptsoft.com).

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: Click Here . Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)