Chapter 1. New and Changed Information

This chapter contains the following sections:

- New and Changed Information

New and Changed Information

The following table provides an overview of the significant changes made to this configuration guide. The table does not provide an exhaustive list of all changes made to this guide or all new features in a particular release.

Feature

Added or Changed in Release

Where Documented

No updates in Cisco NX-OS 7.0(3)I7(3)

7.0(3)I7(3)

This guide.

Chapter 2. Verified Scalability

This document includes the following sections:

- Cisco Nexus 3548 Switch Verified Scalability for NX-OS Release

- Verified Scalability Limits

Cisco Nexus 3548 Switch Verified Scalability for NX-OS Release

This document lists the Cisco verified limits for topologies that include Layer 2 and Layer 3 feature configurations.

In the following tables, the Verified Topology column lists the verified scaling capabilities with all listed features enabled at the same time. The numbers listed here exceed those used by most customers in their topologies. The scale numbers listed here are not the maximum verified values if each feature is viewed in isolation.

The Verified Maximum column lists the maximum scale capability tested for the corresponding feature individually. This number is the absolute maximum currently supported by the Cisco NX-OS Release software for the corresponding feature. If the hardware is capable of a higher scale, future software releases may increase this verified maximum limit.

Note

If your scale requirements exceed either the Verified Topology or the Verified Maximum limit, please contact your Cisco representative. Based on your requirements, it may be possible to validate support for your requirement, as long as the scale capability of the hardware is not exceeded.

Verified Scalability Limits

The tables in this section list the verified scalability limits for Cisco NX-OS Release 7.0(3)I7(3).

Layer 2 and Layer 3 Topology Configuration Limits

Feature

Verified Topology

Verified Maximum

Active VLANs per switch

507 (vPC - normal mode)

507 (with RSTP)

4000 (with MSTP)

BFD neighbors

0

32

MTU

9,216

9,216

STP logical interfaces

2,500

9,000

MST instances

63

64

MAC table size

8,192

40,000 (vPC , Normal mode)

65,532 (non-vPC , Normal mode)

8,192 (non-vPC , Warp mode)

Port Channels

40 vPC port-channels

8 non-vPC port-channels

40 vPC port-channels

24 non-vPC port-channels

Number of member ports per Port Channel

16

24

Number of system logging destination ports

0

8

SPAN sessions

4 active sessions

[1]

4 active bi-directional sessions[2]

1 destination ports per session

Layer 3 physical interfaces

10

48

Layer 3 SVI, subinterfaces, EtherChannels

256

1,024

VRF

10

200

IPv4 hosts

4,096

65,535

IPv4 routes (LPM)

8192 (vPC , Normal mode)

4096 (non-vPC , Warp mode)

24,576 (vPC , Normal mode )

24,576 (non-vPC , Normal mode )

4096 (non-vPC , Warp mode)

Multicast routes

4000 (vPC , Normal mode)

7,990 (non-vPC , Warp mode)

4000 (vPC , Normal mode)

8,192 (non-vPC , Normal mode)

IGMP Snooping groups

3,000

8,192

ECMP[3]

2-way

32-way

TCAM entries for ACL

384 ingress (Normal mode) 128 ingress (Warp mode)

3,000 ingress, 1,000 egress (Normal mode)

HSRP

256

500

VRRP

250[4]

256[5]

Configurable QoS groups

4

4

BGP neighbors

85

100

OSPF neighbors

150 (in a single area, area 0)

150 (in a single area, area 0)

PIM neighbors

250

250

NAT translations

—

1023

[1] Allows same SPAN source in a single direction in 2 SPAN sessions with difference destinations.

[2] 4 active SPAN sessions regardless of the direction of the SPAN session.

[3] Only supported in Normal Traffic Forwarding mode.

[4] A combination of HSRP and VRRP groups, where the total is 250.

[5] A combination of HSRP and VRRP groups, where the total is 250.

Note

The following non-default CoPP values were used for some protocols for the verified topology scale numbers.

Non-Default CoPP Values Used for vPC Verified Topology

Default Values

Non-Default Values

class copp-s-routingProto2
police pps 1300
class copp-s-routingProto1
police pps 1000
class copp-s-pimreg
police pps 200
class copp-s-lldp
police pps 500

class copp-s-routingProto2
police pps 500
class copp-s-routingProto1
police pps 1500
class copp-s-pimreg
police pps 600
class copp-s-lldp
police pps 800

Non-VPC Scale Numbers of Cisco Nexus N3548-X Switches

Feature

Verified Topology

Verified Maximum

Active VLANs per switch

605 (MST Mode)

507 (RSTP Mode)

4013 ( MSTP Mode)

BFD neighbors

16

32

MTU

9,216

9,216

STP logical interfaces

2,500

9000

MST instances

1

64

MAC table size

7375 (90% approx.)

65532 (Non-warp Mode)

8192 (Warp Mode)

Port Channels

7 Non-vPC port-channels

24

Number of member ports per Port Channel

9

24

Number of system logging destination ports

0

8

SPAN sessions

4 Active sessions

[6]

4

Layer 3 physical interfaces

10

48

Layer 3 SVI, subinterfaces, EtherChannels

250

1024

VRF

11

200

IPv4 hosts

7400 (90% approx.)

65,535 (Normal Mode)

8196 (Warp Mode)

IPv4 routes (LPM)

3700 (Non-vPC , WARP mode)

24,576 (Non-vPC, Normal Mode)

4096 (Warp Mode)

Multicast routes

3680 (Non-vPC, WARP mode)

8192 (VPC Normal Mode)

4096 (Non-VPC, Normal Mode)

IGMP Snooping groups

3,000

8192

ECMP

[7]

2-way

32-way

TCAM entries for ACL

384 ingress (Normal mode)

128 ingress (WARP mode)

3000 Ingress, 1000 Egress

HSRP

256

500

VRRP

250

[8]

256

Configurable QoS groups

4

4

BGP neighbors

10

100

OSPF neighbors

10 (in a single area, area 0)

150

PIM neighbors

100

250

NAT translations

10

1023

Multicast Service Reflection sessions

400

1023 (Regular mode)

2047 (Fast Pass mode)

[6] Allows same SPAN source in a single direction in 2 SPAN sessions with difference destinations.

[7] Only supported in Normal Traffic Forwarding mode.

[8] A combination of HSRP and VRRP groups, where the total is 250.

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. (https://www.openssl.org/)

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: https://www.cisco.com/go/trademarks. 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)

Preface

The preface contains the following sections:

- Audience

- Document Conventions

- Obtaining Documentation and Submitting a Service Request

- Documentation Feedback

- Related Documentation for Cisco Nexus 3000 Series Switches

Audience

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

Document 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.

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: http://www.cisco.com/c/en/us/td/docs/general/whatsnew/whatsnew.html.

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.

Documentation Feedback

To provide technical feedback on this document, or to report an error or omission, please send your comments to nexus3k-docfeedback@cisco.com. We appreciate your feedback.

Related Documentation for Cisco Nexus 3000 Series Switches

The entire Cisco Nexus 3000 Series switch documentation set is available at the following URL:

https://www.cisco.com/c/en/us/support/switches/nexus-3000-series-switches/tsd-products-support-series-home.html

Full Cisco Trademarks with Software License

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.

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: https://www.cisco.com/go/trademarks. 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. (1721R)

Insert concept topicref

Insert task topicref

Insert reference topicref

Insert concept topicref

Insert task topicref

Insert reference topicref