b Cisco Nexus 7000 Series NX-OS Verified Scalability Guide

Cisco Nexus 7000 Series NX-OS VerifiedScalability Guide

This document describes the Cisco NX-OS configuration limits for the Cisco Nexus 7000 Series switches.

New and Changed Information, page 1

Introduction, page 3

Configuration Limits for Connecting Cisco Nexus 2000 Series Fabric Extenders to Cisco Nexus 7000Series Switches, page 4

Configuration Limits for FabricPath, page 4

Configuration Limits for FCoE, page 5

Configuration Limits for Interfaces, page 6

Configuration Limits for Layer 2 Switching, page 9

Configuration Limits for LISP, page 10

Configuration Limits for MPLS, page 10

Configuration Limits for Multicast Routing, page 13

Configuration Limits for OTV, page 15

Configuration Limits for QoS, page 16

Configuration Limits for Security, page 16

Configuration Limits for System Management, page 17

Configuration Limits for Unicast Routing, page 18

Configuration Limits for VDCs, page 25

New and Changed InformationThis table summarizes the new and changed verified scalability values for the Cisco Nexus 7000 Seriesswitches.

Cisco Nexus 7000 Series NX-OS Verified Scalability Guide OL-25829-03 1

Table 1: New and Changed Verified Scalability Values

Changed inRelease

DescriptionDate

6.2(6) Added values for private VLANs to the table in the"Configuration Limits for Layer 2 Switching" section.

Added values for the number of secondary IP addressesused for OTV traffic depolarization to the table in the"Configuration Limits for OTV" section.

Added values for the number of physical port vPCs onfront panel ports used for FCoE to the table in the"Configuration Limits for Interfaces" section.

February 24, 2014

6.2Added a new parameter to the table in the "Guidelines andLimitations for EIGRP Configuration Limits" section.

January 8, 2014

6.2Removed the outdated values for "Number of neighbors +passive interfaces + routes" in the "Guidelines and Limitationsfor EIGRP Configuration Limits" section.

January 7, 2014

6.2(6) Updated the EIGRP verified scalability numbers inTable 14 (Configuration Limits for Unicast Routing)for Cisco NX-OS Release 6.2(6).

Updated the configuration limits for Cisco NX-OSRelease 6.2(6) in the "Guidelines and Limitations forEIGRP Configuration Limits" section.

January 6, 2014

6.2 Added the specified I/O modules to introductoryparagraphs for vPC+ and vPC guidelines and limitationsin Cisco NX-OS 6.2 releases.

Updated and added the information for validated VPCscalability in Cisco NX-OS 6.2 releases.

November 2013

6.2.2Updated the verified scalability values.August 2013

6.1.2Updated the verified scalability values.October 2012

6.1Updated the verified scalability values.August 2012

Initial version ofthe guide with information for shippingreleases.

November 2011

Cisco Nexus 7000 Series NX-OS Verified Scalability Guide2 OL-25829-03

Cisco Nexus 7000 Series NX-OS Verified Scalability GuideNew and Changed Information

IntroductionThe scalability of Cisco Nexus 7000 Series switches has been verified for the following features:

Cisco Nexus 2000 Series Fabric Extender connectivity to Cisco Nexus 7000 Series switches

FabricPath

Fibre Channel over Ethernet (FCoE)

Interfaces

Layer 2 switching

Locator/ID Separation Protocol (LISP)

Multiprotocol Label Switching (MPLS)

Multicast routing

Overlay Transport Virtualization (OTV)

QoS

Security

System management

Unicast routing

Virtual device context (VDC)

To make the best use of this document, please take note of the following:

All numbers are per system unless noted otherwise. For example, a listed number of FCoE fabric loginscan be in a single VDC or be a sum of fabric logins across all VDCs in the system. Any changes in thenumber of supported VDCs do not automatically imply changes in the supported scale for other features.

If the latest release has an updated value for a parameter but the previous release does not, specificinformation for the previous release is not available.

The values provided in this guide are uni-dimensional. They focus on the scalability of one particularfeature at a time. Results might differ from the values listed here when trying to achieve maximumscalability with multiple features enabled.

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

Cisco NX-OS Release 6.1 introduced support for Cisco Nexus 7000 Supervisor 2 and Supervisor 2e.Supervisor 2e is designed to provide the highest software scalability. If a higher scale is verified onSupervisor 2e, the scale values for each supervisor will be listed using the following notation: Supervisor1 value / Supervisor 2 value / Supervisor 2e value. If Supervisor 2e is not verified to provide a higherscale for a particular feature parameter, a single scalability value will be listed for all supervisors.

Cisco NX-OS Release 6.2 introduced support for Cisco Nexus 7700 switches. Supervisor 2e runningon Cisco Nexus 7700 switches provides the same software scalability as Supervisor 2e running on CiscoNexus 7000 switches.


Cisco Nexus 7000 Series NX-OS Verified Scalability GuideIntroduction

Configuration Limits for Connecting Cisco Nexus 2000 SeriesFabric Extenders to Cisco Nexus 7000 Series Switches

Table 2: Configuration Limits for Connecting Cisco Nexus 2000 Series Fabric Extenders to Cisco Nexus 7000 SeriesSwitches

Verified Limit(Cisco NX-OS5.2)




Parameter

323232 with 153632 with 1536Number of Fabric Extenders with totalnumber of Fabric Extender serverinterfaces on Supervisor 1 or 2

N/AN/A48 with 204864 with 3072Number of Fabric Extenders with totalnumber of Fabric Extender serverinterfaces on Supervisor 2e

2000200020002000Number of VLANs per FabricExtender

50505075Number of VLANs per FabricExtender server interface

63636363Number of subinterfaces per FabricExtender server interface

To achieve the highest VLAN per Fabric Extender (FEX) port scale, Cisco recommends connecting FEXuplinks to one switch on chip (SoC) on F2 or F2e Series modules instead of spreading them across differentSoCs.

Note

Configuration Limits for FabricPathTable 3: Configuration Limits for FabricPath





Feature

200020002000 (CiscoNX-OS 6.1.1)4000 (CiscoNX-OS 6.1.2)

4000Number of VLANs per switch


Cisco Nexus 7000 Series NX-OS Verified Scalability GuideConfiguration Limits for Connecting Cisco Nexus 2000 Series Fabric Extenders to Cisco Nexus 7000 Series Switches





Feature

256256256256 / 256 / 768Number of core ports per switch

256256256384Number of edge ports per switch

1118Number of topologies

2222Number of trees per topology

10,00010,00010,00010,000Number of multicast groups perswitch

256256256256 / 256 / 768Number of FabricPath IS-ISadjacencies

64128128 (CiscoNX-OS 6.1.1)256 (CiscoNX-OS 6.1.2)

256 / 256 / 768Number of switch IDs

To achieve the maximum number of topologies, Cisco recommends enabling the no port-channel limitcommand. Enabling this command will cause a brief disruption to traffic.

Note

Configuration Limits for FCoETable 4: Configuration Limits for FCoE

Verified Limit(Cisco NX-OS 5.2)




Parameter

Not testedNot testedNot tested2500Number of fabric logins perswitch

Not testedNot testedNot tested500Number of fabric logins perline card

Not testedNot testedNot tested256Number of fabric logins perport

Not testedNot testedNot tested7Number of FCoE hops

Not testedNot testedNot tested396Number of vFC interfaces

Not testedNot testedNot tested128Number of vFC portchannels


Cisco Nexus 7000 Series NX-OS Verified Scalability GuideConfiguration Limits for FCoE





Parameter

Not testedNot testedNot tested16,000Number of zone membersper fabric

Not testedNot testedNot tested8000Number of zones per fabric

Not testedNot testedNot tested500Number of zone sets perswitch

Not testedNot testedNot tested80Number of VSANs perfabric

The numbers above are verified and supported on Cisco Nexus 7000 and Cisco Nexus 7700 switches withSupervisor 2e only.

Note

Configuration Limits for InterfacesTable 5: Configuration Limits for Interfaces





ParameterFeature

528528528744Number of port channels persystem

Port channels

528528528744Number of vPCs (total) persystem

Virtual portchannels(vPCs)

528528528744Number of vPCs (FEX) persystem

2442442443841Number of vPC+s (total) persystem

N/AN/AN/A30 for CiscoNX-OSRelease6.2(6)

Number of physical port vPCson front panel ports used forFCoE


Cisco Nexus 7000 Series NX-OS Verified Scalability GuideConfiguration Limits for Interfaces





ParameterFeature

50 msec x 350 msec x 350 msec x 350 msec x 3Minimum interval x multiplier(peers over Layer 3 link orLayer 3 port channel withper-link mode)

BFD

250 msec x 3250 msec x 3250 msec x 3250 msec x 3Minimum interval x multiplier(peers over Layer 2 portchannel and Layer 3 portchannel without per-linkmode)

N/AN/AN/A1000Number of sessions per I/Omodule with subinterfaceoptimize

Not testedNot testedNot tested500Number of sessions per I/Omodule with 300 msec x 3interval

200200200250Number of sessions per I/Omodule with 50 msec x 3interval

1000100010002000Number of sessions per system

1500150015001500Number of GRE tunnelsGenericroutingencapsulation(GRE)

1 To achieve more than 244 VPC+s, you must enable the no port-channel limit command. Enabling this command will cause a brief disruption to traffic.

Guidelines and Limitations for vPC Configuration Limits

The vPC configuration limits such as the number of vPC+ and VLANs in a vPC+ domain depend on manydifferent parameters. The following templates are validated in the Cisco NX-OS 6.2 release with M2 and F2eI/O modules where applicable and should be used as a guide in planning your deployment.

Profile DProfile CProfile BProfile A2Profile A1Feature

744400357575vPC

11141VDC

400040004000500500VLANs persystem

20030040003030VLAN trunkedper vPC

74440004000300500SVI per system



Profile DProfile CProfile BProfile A2Profile A1Feature

N/A -- MSTused

N/A -- MSTused

N/A -- MSTused

16,0006,500RPVST+logical ports

150,000150,000150,000150,00090,000STP virtualports

74440004000300500HSRP groups

2e2e2e2e1Supervisor

For the highest vPC scalability, Cisco recommends deploying MST and Supervisor 2e. For scenarios with4000 VLANs or SVIs and HSRP, Cisco recommends using the M2 Series modules.

Note

Guidelines and Limitations for vPC+ Configuration Limits

The vPC+ configuration limits such as the number of vPC+ and VLANs in a vPC+ domain depend on manydifferent parameters. The following templates are validated in the Cisco NX-OS 6.2 release with F2e I/Omodules and should be used as a guide in planning your deployment.

Profile BProfile AFeature

35384vPC+

12VDC

40002000VLANs per VDC

400075VLAN / vPC

4000384HSRP groups

2e2eSupervisor

Guidelines and Limitations for BFD Configuration Limits

Beginning with Cisco NX-OS Release 6.2, the number of sessions can be all IPv4, all IPv6, or a mix ofboth.

For the highest per-line card scale, Cisco recommends using the M2, F2, or F2e Series modules.

For the highest per-system scale, Cisco recommends using Supervisor 2e.



Configuration Limits for Layer 2 SwitchingTable 6: Configuration Limits for Layer 2 Switching





ParameterFeature

128,000128,000128,000128,000Number of Layer 2 tableentries on M Series I/Omodules

Layer 2infrastructure

16,000 to256,000

16,000 to256,000

16,000 to256,000

16,000 to256,000

Number of Layer 2 tableentries on F1 Series I/Omodules

N/A16,000 to192,000

16,000 to192,000

16,000 to192,000

Number of Layer 2 tableentries on F2 or F2e SeriesI/O modules

64646464Number of MultipleSpanning Tree (MST)instances per VDC

Spanning TreeProtocol

90,00090,00090,00090,000 /90,000 /150,000

Number of MST virtualports

16,00016,00016,00016,000Number of Rapidper-VLAN SpanningTree+ (RPVST+) logicalports per switch

16161616Number of private VLANmappings perpromiscuous trunk

Private VLAN

The F2 and F2e modules synchronize the MAC address tables for a VLAN across all Switch on Chips(SoCs) present in a virtual device context (VDC) when a switch virtual interface (SVI) for the VLAN isconfigured. Synchronizing the MAC address tables can reduce the number of MAC addresses supportedin a VDC to 16,000.

Note


Cisco Nexus 7000 Series NX-OS Verified Scalability GuideConfiguration Limits for Layer 2 Switching

Configuration Limits for LISPTable 7: Configuration Limits for Map Server and Ingress Tunnel Routers (ITRs) and Egress Tunnel Routers (ETRs)

VerifiedLimit (CiscoNX-OS 5.2)




ParameterFeature

100010,00010,00010,000Number of mapping entriesregistered on a map server

Map server

8888Number of RLOCs per EIDmapping entry

250250250250Number of dynamic EIDmappingentries registered to a map server

ITR/ETR

4444Number of EIDs with staticmapping entries registered to amap server (per address family andper VRF)

300300300300Number of VRFs

N/AN/AN/A256Number of instances on a mapserver

Multi-Tenancy

N/AN/AN/A256Number of instances on xTR andPxTR

Not testedNot testedNot tested1000Number of EID prefixes on PxTRmap cache

PxTR

Not testedNot testedNot tested10,000Number of EID prefixes on xTRmap cache

xTR

Configuration Limits for MPLSTable 8: Configuration Limits for MPLS





ParameterFeature

4444Maximum labeldepth for forwarding

LDP andinfrastructure

200200200200Number of LDPsessions


Cisco Nexus 7000 Series NX-OS Verified Scalability GuideConfiguration Limits for LISP





ParameterFeature

4000400040005000Number of MPLSTE head-end tunnels

Trafficengineering

12,00012,00012,00012,000Number of MPLSTE mid-point LSPs(transit)

N/AN/AN/A2000Number ofpseudo-wires forVPLS

Layer 2VPN(L2VPN)

N/AN/AN/A4000Number ofpseudo-wires forEoMPLS

N/AN/AN/A1000Number of VPLSvirtual forwardinginstances (VFIs)

N/AN/AN/A1000Number of VPLSbridge domains

N/AN/AN/A16 single-homed8 dual-homed

Number of VPLSsites

N/AN/AN/A40,000Number of MACaddresses in VPLSacross all VLANs


Cisco Nexus 7000 Series NX-OS Verified Scalability GuideConfiguration Limits for MPLS





ParameterFeature

1000100010001000 / 1000 /4000

Number of VPNsper system

Layer 3VPN(L3VPN)

300,000300,000300,000300,000 /300,000 /500,000

Number of VPNv4routes withper-prefix labelallocation mode

300,000300,000300,000300,000 /300,000 /500,000

Number of VPNlabels withper-prefix labelallocation mode

500,000500,000500,000500,000 /500,000 /700,000

Number of VPNv4routes with per-VRFlabel allocationmode

1000100010001000 / 1000 /4000

Number of VPNlabels with per-VRFlabel allocationmode

250,000250,000250,000250,000 /250,000 /350,000

Number of VPNv6(6VPE) routes withper-VRF labelallocation mode

Not testedNot testedNot tested1000Number of routetargets imported inone VRF

200200200200Number of multicastVRFs per system

MVPN

50,00050,00050,00050,000Number of multicastVRF routes

1000100010001000Number of MDTgroups per system

2562562561000Number of MDTgroups per VRF

Guidelines and Limitations for MPLS L2VPN Configuration Limits

Each MPLS L2VPN scale value might vary when combined with other parameters.

For VPLS, the more sites that are used, the fewer VFIs and bridge domains that can be supported dueto the increased number of pseudo-wires to connect sites in a full mesh.


Cisco Nexus 7000 Series NX-OS Verified Scalability GuideConfiguration Limits for MPLS

Guidelines and Limitations for MPLS L3VPN Configuration Limits

Each MPLS L3VPN scale value might vary when combined with other parameters. See examples ofscenarios tested with Supervisor 2e running Cisco NX-OS Release 6.2 for better guidance.

The following scenarios were tested in a single VDC as well as in VRFs broken up across four VDCs.85% of the routes were local, and 15% were remote.

Verified Limit (Cisco NX-OS6.2)

Parameter

4000Number of L3VPNswith PE-CE (2000 static routes + 2000BGP sessions)

4000Number of L3VPNs without PE-CE (direct routes)

4000Number of L3VPNs in InterAS OptB lite

Configuration Limits for Multicast RoutingTable 9: Configuration Limits for Multicast Routing





ParameterFeature

32,00032,00032,00032,000Number of IPv4 multicastroutes with PIM sparse mode

Multicastrouting andforwarding

Not testedNot testedNot tested32,000Number of IPv4 multicastroutes with PIM bidirectional

16,000 / 816,000 / 816,000 / 816,000 / 8Number of IPv4 multicastroutes using generic routingencapsulation reverse pathforwarding (GRE RPF)interfaces or outgoinginterfaces (OIFs) / number ofGRE OIFs per route

15,00015,00015,00025,000Number of IPv4 multicastroutes in a vPC environment

2000200020002000Number of IPv6 multicastroutes


Cisco Nexus 7000 Series NX-OS Verified Scalability GuideConfiguration Limits for Multicast Routing





ParameterFeature

32,00032,00032,00032,0002Number of IGMP groupsInternetGroupManagementProtocol(IGMP) andMulticastListenerDiscovery(MLD)

2000200020002000Number of MLD groups

12,00012,00012,00012,000Number of MSDPsource-active (SA) cacheentries

MulticastSourceDiscoveryProtocol(MSDP) 6666Number of MSDP peers

1000100010001000Number of PIM IPv4neighbors

PIM

Not testedNot testedNot tested50Number of PIM IPv4neighbors with aggressivehello/hold timers (1 second / 3seconds)

Not testedNot testedNot tested200Number of PIM IPv6neighbors

2 4000 mroutes were (*,G), and the rest were (S,G).

Cisco recommends M2 Series modules to achieve the highest multicast scale.Note

High availability (stateful switchover and ISSU) is not supported with aggressive PIM hello timers. Ciscorecommends using default PIM hello timers combined with BFD for PIM.

Note


Cisco Nexus 7000 Series NX-OS Verified Scalability GuideConfiguration Limits for Multicast Routing

Configuration Limits for OTVTable 10: Configuration Limits for OTV





Parameter

2562562561500Number of extended VLANs persystem across all configuredoverlays

16,00016,00016,00032,000Number of total MAC addressesacross all sites

8,0008,0008,00012,000Number of local MAC addressesper site

2222Number of edge devices per site

6668Number of OTV-connected sites

10101010Number of OTV overlays(simultaneous)

1111Number of instances (instance-id)

2000200020004000Number of local multicast routes

256256256256Number of multicast data groups

N/AN/AN/A3 from CiscoNX-OS Release6.2(6)

Number of secondary IP addressesused for OTV traffic depolarization

To achieve maximum VLAN and MAC address scale, Cisco recommends using one overlay.Note


Cisco Nexus 7000 Series NX-OS Verified Scalability GuideConfiguration Limits for OTV

Configuration Limits for QoSTable 11: Configuration Limits for QoS

Verified Limit(Cisco NX-OSRelease 5.2)




Parameter

128128128128Number of class maps perpolicy

1024102410241024Number of matches in aclass map

16,00016,00016,00016,000Number of policers

Configuration Limits for SecurityTable 12: Configuration Limits for Security





ParameterFeature

1000100010001000Maximum number of ACEs forapplication ACLs (used byNTP, SNMP, and VTY)

ACLs

1111Number of sessions per systemACL capture

Not testedNot testedNot tested50,000Number of IP-SGT mappingsCisco TrustSec

Not testedNot tested400050,000Number of total bindings forDHCPv4 snooping

DHCP

Not testedNot tested10004000Number of VLANs for DHCPsnooping

Not testedNot tested400050,000Number of total clients forDHCPv4 relay

N/AN/AN/A10,000Number of total clients forDHCPv6 relay

Not testedNot tested10003960Number of DHCP relay agents

Not testedNot tested1616Number of DHCP helperaddresses for SVI


Cisco Nexus 7000 Series NX-OS Verified Scalability GuideConfiguration Limits for QoS

Each DHCP scale value might vary when combined with other parameters. See this example of a scenariotested for Cisco NX-OS Release 6.2 for better guidance.


Parameter

3960Number of SVIs with IPv4 and IPv6 DHCP relay configured together

Guidelines and Limitations for DHCP Configuration Limits

For Cisco NX-OS Release 6.2 and later releases, you must enable the insertion of Option 82 information forDHCP packets to support the highest DHCP snooping scale.

Configuration Limits for System ManagementTable 13: Configuration Limits for System Management





ParameterFeature

N/AN/A500500 / 500 /10003

Maximum number of probesconfigured

IP SLA

22214 (Nexus7000); 16(Nexus7700)

Number of active SPAN or ERSPANsource sessions per system

SPAN andERSPAN

48484848Number of configured (not active)SPAN sessions per VDC

23232323 (Nexus7000); 16(Nexus7700)

Number of active ERSPANdestination sessions per system

128128128128Number of source interfaces perSPAN or ERSPAN session

32323232Number of destination interfaces perSPAN or ERSPAN session

32323232Number of source VLANs per SPANor ERSPAN session

Not testedNot tested100 / 100 /512

100 / 100 /512

Number of clients behind a portPTP/IEEE1588

3 The highest scale was verified with UDP jitter and ICMP probes.


Cisco Nexus 7000 Series NX-OS Verified Scalability GuideConfiguration Limits for System Management

Guidelines and Limitations for IP SLA Configuration Limits

To achieve the highest IP SLA probe scale, you might need to add a specific CoPP configuration toallow the IP SLA generated packets to pass through. Otherwise, probes might experience timeouts. Seethe Cisco Nexus 7000 Series NX-OS IP SLAs Configuration Guide for more details.

Even if CoPP is not dropping any IP SLA traffic, round-trip times (RTTs) might vary, so it is importantto test locally and set the proper timeout value for IP SLA probes. Generally, Cisco does not recommendsetting the IP SLA probe timeout below 1 second.

Cisco recommends using Supervisor 2e to achieve the highest scale and the lowest RTT for IP SLAprobes.

Guidelines and Limitations for SPAN Configuration Limits

The number of SPAN sessions refers to unidirectional sessions. On the Cisco Nexus 7000 Series switch, twoSPAN extended sessions can be combined to create a bidirectional session, and a SPAN standard session canbehave either as unidirectional or bidirectional. The Cisco Nexus 7700 switch does not have standard andextended sessions. All SPAN sessions are unidirectional, and any two can be combined to create a bidirectionalsession. See the Cisco Nexus 7000 Series NX-OS System Management Configuration Guide for moreinformation.

Configuration Limits for Unicast RoutingTable 14: Configuration Limits for Unicast Routing





ParameterFeature

128,000128,000128,000128,000Number of entries in ARP tableARP/ND


Number of ARP packets persecond


Number of ARP glean packetsfor second


Number of IPv6 ND packetsper second


Number of IPv6 glean packetsper second


Cisco Nexus 7000 Series NX-OS Verified Scalability GuideConfiguration Limits for Unicast Routing





ParameterFeature

300 / 15,000300 / 15,000300 / 15,0001000 / 100,000Number of neighbors / totalLSAs4

OSPFv2

16 / 600016 / 600016 / 6000250 / 50,000Number of neighbors / totalLSAs with aggressive timers(1s/4s)5

5005005003780Number of passive interfaces

441616Number of process instancesper VDC

16161616Number of process instancesper system

16161632Number of equal cost paths

300 / 15,000300 / 15,000300 / 15,000300 / 50,000Number of neighbors / totalLSAs6

OSPFv3

3003003001280Number of passive interfaces




300300300300Number of neighborsIS-IS

Not testedNot testedNot tested250Number of neighbors withaggressive timers (1s/3s)

Not testedNot testedNot tested600Number of passive interfaces

Not testedNot testedNot tested30,000Number of routes










ParameterFeature

50503005002000 in 6.2(6)and laterreleases

Number of neighborsEIGRP

Not testedNot testedNot tested250Number of neighbors withaggressive timers (1s/3s)

Not testedNot testedNot tested3960Number of passive interfaces

15,00015,00015,00050,000100,000 in6.2(6) andlater releases

Number of routes




1000100010004000Number of static routesStaticrouting

1000100010002000Number of peersBGP

512512512512Number of AS-path entries

20,00020,00020,00020,000Number of prefix-list entries ina single prefix list

900,000900,000900,000900,000Number of prefixes per peer(one peer, eBGP or iBGP,IPv4)

3 million3 million3 million5.2 millionNumber of routes in BGP RIB

512,000512,000512,000920,000Number of unique attributesstored in BGP database


N/AN/A3232Number of paths advertisedwith BGP addpath7







ParameterFeature

500500500No limitNumber of groups per interfaceor I/O module

HSRP

N/AN/AN/A2000 / 2000 /4000 (withmaximum2000 mastergroups)

Number of groups with defaulttimers (3s/10s) and multiplegroup optimization

2000200020002000Number of groups with defaulttimers (3s/10s)

1000100010001000Number of groups withaggressive timers (1s/3s) andextended hold timer features(in-service software upgrade[ISSU] / stateful switchover[SSO] support)

N/AN/AN/A4Number of routers in AnycastHSRP group

AnycastHSRP

N/AN/AN/A64 (Nexus7000)128 (Nexus7700)

Number of Anycast HSRPbundles

N/AN/AN/A200Number of groups per bundle

N/AN/AN/A2000Number of groups across allAnycast HSRP bundles

100100100100Number of groups per interfaceor I/O module

VRRPv2


N/AN/AN/A255 / 255 /4000 (withmaximum2000 leadergroups)

Number of groups with relaxedtimers (3s/10s) and pathways

VRRPv3

N/AN/AN/A255 / 255 /2000

Number of groups with relaxedtimers (3s/10s)

N/AN/AN/A255 / 255 /1000

Number of groups with defaulttimers (1s/3s)







ParameterFeature

200200200200Number of groups per interfaceor I/O module

GLBP


500500500500Number of groups withaggressive timers (1s/3s)

500500500500Number of groups withaggressive timers (1s/3s) andextended hold timer feature(ISSU/SSO support)

Not testedNot tested23 (startingwith CiscoNX-OS 6.1.3)

23Number of configuredsequences per policy

PBR

Not testedNot testedNot tested500Number of objects trackedObjecttracking

1000100010004000Number of VRFs per system8,9

VRFs

4 The number of LSAs equals the number of routes.5 The number of LSAs equals the number of routes.6 The number of LSAs equals the number of routes.7 Only 16 paths are active and programmed to the hardware in Cisco NX-OS Release 6.1. Beginning with Cisco NX-OS Release 6.2 with F2 or F2e Series

modules, 32 paths can be active and programmed to the hardware.8 With each new VDC configured, the number of configurable VRFs per system is reduced by two as each VDC has a default VRF and management VRFs that

are not removable. For example, with 4 configured VDCs on Cisco NX-OS Release 6.2, you can configure up to 992 additional VRFs per system (either allin one VDC or across VDCs).

9 Not all dynamic routing protocols can support having peers in all of the supported VRFs. Refer to the individual protocol scale for more information.

Guidelines and Limitations for All Unicast Routing Configuration Limits

32-way ECMP is supported only with F2 and F2e Series modules and Cisco NX-OS Release 6.2.

High availability (graceful restart, stateful switchover, and ISSU) is not supported when protocolaggressive timers are configured at any scale.

Guidelines and Limitations for OSPF Configuration Limits

Cisco recommends using Supervisor 2e for the highest scale and fastest convergence.

To achieve the highest scale, Cisco recommends using a single OSPF instance instead of multipleinstances.

Each OSPFv2 and OSPFv3 scale value might vary when combined with other parameters. See examplesof scenarios tested for Cisco NX-OS Release 6.2 for better guidance. All scenarios were tested with asingle OSPF instance.



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

The passive interface default was used.

Verified Limit (CiscoNX-OS 6.2)

ParameterFeature

1000 + 2899 + 100,000 +300

Number of maximum neighbors + passive interfaces + total LSAs+ VRFs

OSPFv2

1003 + 2899 + 100,000Number of maximum neighbors + passive interfaces + total LSAsOSPFv2

3780 + 22 + 100,000Number of maximum passive interfaces + neighbors + total LSAsOSPFv2

250 + 750 + 50,000 + 250Number of neighbors + passive interfaces + total LSAs + VRFswith aggressive timers (1s/4s)

OSPFv2

300 + 1000 + 50,000 +300

Number of maximum neighbors + passive interfaces + total LSAs+ VRFs

OSPFv3

1280 + 20 + 50,000Number of maximum passive interfaces + neighbors + total LSAsOSPFv3

100 + 300 + 25,000 + 100Number of neighbors + passive interfaces + total LSAs + VRFswith aggressive timers (1s/4s)

OSPFv3

Guidelines and Limitations for IS-IS Configuration Limits

Cisco recommends using Supervisor 2e for the highest scale and fastest convergence.

Each IS-IS scale valuemight vary when combined with other parameters. See these examples of scenariostested for Cisco NX-OS Release 6.2 for better guidance. All scenarios were tested with a single IS-ISinstance with IPv4 and IPv6 address families enabled on all peers and the total number of routes beinga mix of IPv4 and IPv6 routes.


Parameter

300 + 600 + 30,000Number of maximum neighbors + passive interfaces + total routes

300 + 600 + 30,000Number of maximum passive interfaces + neighbors + total routes

250 + 600 + 30,000Number of neighbors + passive interfaces + total routes with aggressivetimers (1s/3s)

Guidelines and Limitations for EIGRP Configuration Limits

The passive interface default was used.

To achieve the highest scale with high availability, you must increase the graceful restart signal timerto 60 seconds.

Each EIGRP scale value might vary when combined with other parameters. See these examples ofscenarios tested for Cisco NX-OS Release 6.2 for better guidance. All scenarios were tested with a singleEIGRP instance.




Parameter

300 + 2000 + 30,000 + 30

2000+3960+100,000+1000 in6.2(6) and later releases

Number of neighbors + passive interfaces + routes + VRFs

250 + 1000 + 50,000 + 250Number of neighbors + passive interfaces + routes + VRFs with aggressivetimers (1s/3s)

Guidelines and Limitations for BGP Configuration Limits

Each BGP scale value might vary when combined with other parameters. See these examples of scenariostested for Cisco NX-OS Release 6.2 for better guidance.

All values were tested with default BGP keepalive and hold timers.

All scenarios were tested with the minimum and maximum configured u4route-mem and u6route-memunder the VDC as 350 MB/110 MB respectively.


Parameter

1750 + 250 + 50,000Number of maximum eBGP peers + iBGP peers + total routes (75% IPv4,25% IPv6)

1750 + 250 + 50,000Number of maximum iBGP peers + eBGP peers + total routes (75% IPv4,25% IPv6)

5.2 millionNumber of routes in BGP RIB (75% IPv4, 25% IPv6)

12Number of eBGP peers with Internet feed (440,000 IPv4 routes, 12,000 IPv6routes)

Guidelines and Limitations for HSRP, VRRP, and GLBP Configuration Limits

The number of HSRPv2 and VRRPv3 groups can be IPv4 only, IPv6 only, or a combination of both.For example, if Cisco NX-OS supports 4000 HSRP groups, it can also support 4000 VLANs with eachrunning HSRP IPv4 groups or 2000 dual-stacked VLANs.

The same FHRP group ID or different group IDs can be used in different VLANs and within the sameVLAN for IPv4 and IPv6 groups.



Configuration Limits for VDCsTable 15: Configuration Limits for VDCs





Feature

4 (including 1default VDC)



4+1 (with adminVDC feature)

VDCs with Supervisor1

N/AN/A4+1 (with adminVDC feature)


VDCs with Supervisor2

N/AN/A8+1 (with adminVDC feature)


VDCs with Supervisor2e

64646464VDC resourcetemplates


Cisco Nexus 7000 Series NX-OS Verified Scalability GuideConfiguration Limits for VDCs


Cisco Nexus 7000 Series NX-OS Verified Scalability GuideConfiguration Limits for VDCs

Cisco Nexus 7000 Series NX-OS Verified Scalability GuideNew and Changed InformationIntroductionConfiguration Limits for Connecting Cisco Nexus 2000 Series Fabric Extenders to Cisco Nexus 7000 Series SwitchesConfiguration Limits for FabricPathConfiguration Limits for FCoEConfiguration Limits for InterfacesConfiguration Limits for Layer 2 SwitchingConfiguration Limits for LISPConfiguration Limits for MPLSConfiguration Limits for Multicast RoutingConfiguration Limits for OTVConfiguration Limits for QoSConfiguration Limits for SecurityConfiguration Limits for System ManagementConfiguration Limits for Unicast RoutingConfiguration Limits for VDCs

b Cisco Nexus 7000 Series NX-OS Verified Scalability Guide

Documents

Transcript of b Cisco Nexus 7000 Series NX-OS Verified Scalability Guide