PDF(1.0 MB) View with Adobe Reader on a variety of devices
Updated:July 20, 2017
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes the Cisco NX-OS configuration limits for the Cisco Nexus 31128PQ switch.
The values provided in this guide
should not be interpreted as theoretical system limits for Cisco Nexus 31128PQ
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)I7(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.
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.
Active localized SPAN or ERSPAN sessions per line card3
Source interfaces per SPAN or ERSPAN session (Rx and Tx, Rx, or Tx)
Destination interfaces per SPAN session
1 (physical interface)
Source VLANs per SPAN or ERSPAN session
Redirect interfaces in the redirect port list
Redirect port lists (or fan outs) per system
2 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.
3 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.