Chapter 1. Verified Scalability Limits

Introduction

Verified Scalability Limits (Unidimensional)

Preface

Audience

Documentation Conventions

Documentation Feedback

Obtaining Documentation and Submitting a Service Request

Copyright Page

Chapter 1. Verified Scalability Limits

This chapter describes the Cisco NX-OS configuration limits for the Cisco Nexus 3164Q switch.

- Introduction

- Verified Scalability Limits (Unidimensional)

Introduction

The values provided in this guide should not be interpreted as theoretical system limits for Cisco Nexus 3164Q 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 Releases 6.1(2)I2(2a) and 6.1(2)I2(2b) on the Cisco Nexus 3164Q 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

3164Q Verified Limit

BFD sessions

250

Port channel links

32

SVIs

250

vPCs

60

Layer 2 Switching Verified Scalability Limits (Unidimensional)

Feature

3164Q Verified Limit

MST instances

64

MST virtual ports

48,000

RPVST virtual ports

12,000

VLANs

3900

VLANs in RPVST mode

500

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

3164Q Verified Limit

IPv4 multicast routes

32,000

Outgoing interfaces (OIFs)

40 (see CSCum58876)

IGMP snooping groups

32,000

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

3164Q Verified Limit

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)

System Management Verified Scalability Limits (Unidimensional)

Feature

3164Q Verified Limit

Configurable SPAN or ERSPAN sessions

4

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

[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

3164Q Verified Limit

eBGP

1000

HSRP groups per interface or I/O module

250

IPv4 ARP

48,000

IPv4 host routes

88,000

IPv6 host routes

20,000

IPv6 ND

30,000

IPv4 unicast routes (LPM)

128,000

IPv6 unicast routes (LPM)

16,000

MAC addresses

80,000

OSPFv2 neighbors

200

OSPFv3 neighbors

200

VRRP groups per interface or I/O module

250

VRFs

1000

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

3164Q Verified Limit

Virtual network identifiers (VNIs) or VXLAN-mapped VLANs

640

Overlay multicast groups

128

Overlay MAC addresses

64,000

Remote VXLAN tunnel endpoints (VTEPs)

256

Preface

This preface includes the following sections:

- Audience

- Documentation Conventions

- Documentation Feedback

- Obtaining Documentation and Submitting a Service Request

Audience

This publication is for hardware installers and network administrators who install, configure, and maintain Cisco Nexus switches.

Documentation Conventions

Command descriptions use the following conventions:

Convention

Description

bold

Bold text indicates the commands and keywords that you enter literally as shown.

Italic

Italic text indicates arguments for which the user supplies the values.

[x]

Square brackets enclose an optional element (keyword or argument).

[x | y]

Square brackets enclosing keywords or arguments separated by a vertical bar indicate an optional choice.

{x | y}

Braces enclosing keywords or arguments separated by a vertical bar indicate a required choice.

[x {y | z}]

Nested set of square brackets or braces indicate optional or required choices within optional or required elements. Braces and a vertical bar within square brackets indicate a required choice within an optional element.

variable

Indicates a variable for which you supply values, in context where italics cannot be used.

string

A nonquoted set of characters. Do not use quotation marks around the string or the string will include the quotation marks.

Examples use the following conventions:

Convention

Description

screen font

Terminal sessions and information the switch displays are in screen font.

boldface screen font

Information you must enter is in boldface screen font.

italic screen font

Arguments for which you supply values are in italic screen font.

< >

Nonprinting characters, such as passwords, are in angle brackets.

[ ]

Default responses to system prompts are in square brackets.

!, #

An exclamation point (!) or a pound sign (#) at the beginning of a line of code indicates a comment line.

Documentation Feedback

To provide technical feedback on this document, or to report an error or omission, please send your comments to . We appreciate your feedback.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What's New in Cisco Product Documentation at: Click Here

Subscribe to What’s New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation as an RSS feed and delivers content directly to your desktop using a reader application. The RSS feeds are a free service.

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)