Table Of Contents
Cisco Nexus 1000V Resource Availability Reference, Release 4.2(1)SV2(2.1)
Introduction to Resource Availability
Obtaining Documentation and Submitting a Service Request
Cisco Nexus 1000V Resource Availability Reference, Release 4.2(1)SV2(2.1)
Release Date: September 13, 2013Part Number: OL-29179-01
Current Release: NX-OS Release 4.2(1)SV2(2.1)This document describes the availability of the system-wide resources with respect to the supported configuration limits on the Cisco Nexus 1000V Release 4.2(1)SV2(2.1) software. The following is the change history for this document.
Part Number Revision Date DescriptionOL-29179-01
A0
June 21, 2013
Created Cisco Nexus 1000V Resource Availability Document for Release 4.2(1)SV2(2.1).
OL-29179-01
B0
September 13, 2013
Updated the value of Active VLANs and VXLANs across all VEMs in Table 3.
Contents
This document includes the following sections:
•Introduction to Resource Availability
•Availability of the Resources
•Examples of the Show Commands
Introduction to Resource Availability
Starting with Release 4.2(1)SV2(1.1), the Cisco Nexus 1000V software is enhanced to keep a track of the usage of system-wide resources with respect to the supported configuration limits on Cisco Nexus 1000V. This enhancement to the NX-OS code base implements a series of show commands that display the current and maximum system limits for the various resources and their current availability.
The format for the command is show resource-availability [resource] [module <id>]. The resource is an optional argument that could either be a specific resource, for example, VLAN or all. The module is an optional keyword that is followed by a specific module number argument.
The show resource-availability <resource> command displays the availability information on the distributed virtual switch (DVS) and on each module for the specified resource. The show resource-availability <resource> module <id> command displays the availability information only for the specified module.
The command show resource-availability only displays the DVS-wide availability information about the key resources, for example, hosts, port-profiles, vEthernet ports, port-channels, and VLANs.
The show resource-availability all command prints the availability information on the DVS and each module for all the resources. The CLI is implemented as a sequence of show resource-availability <resource> commands iterating through all the resources.
Note You cannot generate xml output for show resource-availability all command.
The show resource-availability module <id> command displays the availability information for the specified module for all the resources that have a per-module configuration limit. The CLI is implemented as a series of show resource-availability <resource> module <id> commands.
Table 1 lists the resources and the corresponding aggregate commands.
Availability of the Resources
Table 2 lists the resources and the corresponding aggregate commands.
Examples of the Show Commands
Refer to this section for the examples of the show commands to display the availability of the resources.
n1000v# show resource-availability ?
<CR>> Redirect it to a file>> Redirect it to a file in append modeacl Show resource information for Aclall Show resource information for all resourcesbridge-domain Show resource information for bridge-domainsethports Show resource information for ethernet portshosts Show resource information for hostsip Show resource information for IPmac-address-table Show resource information for mac address tablemodule Show resource information for a specific VEMmonitor Show resource information for ethernet spannetflow Show resource information for Netflowport-channel Show resource information for port channelsport-profile Show resource information for port-profilesport-security Show resource information for port securityprivate-vlan Show resource information for private vlanqos-queuing Show resource information for QoS and Queuingvethports Show resource information for vethernet portsvlan Show resource information for vlan| Pipe command output to filtern1000v# show resource-availability acl
Maximum number of access lists per DVS is 128The number of access lists created is 1The number of access lists available is 127Maximum number of ACL Instances per DVS is 4096The number of ACL Instances created is 0The number of ACL instances available is 4096Maximum number of ACL Instances per module is 300Following table shows the per module instance usage----------------------------------------------------------------Module Used Available----------------------------------------------------------------n1000v# show resource-availability all ?
<CR>> Redirect it to a file>> Redirect it to a file in append mode| Pipe command output to filtern1000v# show resource-availability bridge-domain ?
<CR>> Redirect it to a file>> Redirect it to a file in append mode| Pipe command output to filtern1000v# show resource-availability bridge-domain
Maximum number of bridge-domains per DVS: 2048Number of bridge-domains currently created: 2Number of bridge-domains available*: 2046* available bridge-domains do not account for created VLANsn1000v# show resource-availability ethports
Maximum number of Eth ports per module: 32--------------------------------------------------------------------------------Module Used Available--------------------------------------------------------------------------------3 1 314 1 315 2 306 1 31n1000v# show resource-availability hosts
Maximum number of hosts that can be added to DVS: 128Number of hosts currently powered up: 4Number of hosts currently absent: 0Number of hosts that can be added further: 124n1000v# show resource-availability ip igmp snooping
Max number of IGMP groups supported: 512Number of IGMP groups in use: 0Number of IGMP groups available: 512n1000v## show resource-availability mac-address-table
Maximum MAC Addresses per module: 32000--------------------------------------------------------------------------------Module Used Available--------------------------------------------------------------------------------3 83 319174 78 319225 97 319036 86 31914n1000v#k# show resource-availability mac-address-table module 3
Maximum MAC Addresses per module: 32000--------------------------------------------------------------------------------Module Used Available--------------------------------------------------------------------------------3 80 31920n1000v# show resource-availability module ?
<3-130> Enter module numbern1000v# show resource-availability monitor
Maximum number of monitor sessions per DVS: 64Number of monitor sessions in use: 0Number of monitor sessions available: 64Maximum number of source interfaces per session: 128Maximum number of source vlans per session: 32Maximum number of destination interfaces per local monitor session: 32Maximum number of destination IP addresses per erspan-src session: 1Ssn Type Used Src Avl Src Used Src Avl Src Used Dst Avl DstIntf Intf Vlans Vlans--- ---------- -------- -------- -------- -------- -------- --------n1000v# show resource-availability netflow
Maximum number of netflow monitors per DVS is 32The number of monitors created is 0The number of netflow monitors available is 32Maximum number of netflow instances per DVS is 256The number of netflow instances created is 0The number of netflow instances available is 256Maximum number of netflow instances per module is 32Following table shows the per module instance usage----------------------------------------------------------------Module Used Available---------------------------------------------------------------n1000vk# show resource-availability netflow module 3Maximum number of netflow instances per host is 32Instances created is 0Instances available is 32n1000v# show resource-availability port-channel ?
<CR>> Redirect it to a file>> Redirect it to a file in append modemodule Show VEM specific information| Pipe command output to filtern1000v# show resource-availability port-channel
Maximum number of port channels per DVS: 512Number of port channels currently created: 0Number of port channels available: 512Maximum number of port channels per module: 8--------------------------------------------------------------------------------Module Used Available--------------------------------------------------------------------------------3 1 74 1 75 2 66 1 7Note: Modules not seen in above table are either not added to DVS or have all 8port channels availablen1000v# show resource-availability port-channel module ?
<3-66> Enter module numbern1000v# show resource-availability port-channel module 3 ?
Maximum number of port channels per module: 8Number of port channels in module: 1Number of port channels available for module: 7n1000v# show resource-availability port-security macs
----------------------------------------------------Allowed Used Avail----------------------------------------------------8192 0 8192----------------------------------------------------n1000v# show resource-availability private-vlan
Maximum number of Private VLANs per DVS: 512Number of used Private VLANs: 6Number of available Private VLANs : 506Maximum number of Primary VLANs per promiscuous trunk port: 64Maximum number of Private VLAN associations: 511n1000v#k# show resource-availability qos-queuing
Maximum number of classmaps per DVS is 1024The number of classmaps created is 171The number of classmaps available is 853Maximum number of policy maps per DVS is 128The number of policy maps created is 38The number of policy maps available is 90Maximum number of instances per DVS is 4096The number of instances created is 3The number of instances available is 4093Maximum number of instances per module is 300Following table shows the per module instance usage----------------------------------------------------------------Module Used Available----------------------------------------------------------------4 3 297n1000v# show resource-availability qos-queuing module 3Maximum number of instances per host is 300Instances created is 3Instances available is 297n1000v#k# show resource-availability vethports
Maximum number of Veth ports per DVS: 4096Number of Veth ports used: 7Number of Veth ports available : 4089Maximum number of Veth ports per module: 300--------------------------------------------------------------------------------Module Used Available--------------------------------------------------------------------------------3 3 2975 4 296n1000v# show resource-availability vethports module 4Maximum number of Veth ports per module: 300Number of Veth ports in module: 0Number of Veth ports available for module: 300n1000v# show resource-availability vlan
Maximum number of user VLANs supported: 2048Number of user VLANs created : 1035Total number of available user VLANs : 1013Note: Total number of available user VLANs do not account for created bridge-domains.Limitations and Restrictions
The Cisco Nexus 1000V has the following limitations and restrictions:
Configuration Limits
Table 3 shows the Cisco Nexus 1000V configuration limits:
Table 3 Configuration Limits for Cisco Nexus 1000V
Component Supported Limits for a Single Cisco Nexus 1000V Deployment Spanning up to 2 Physical Data CentersMaximum Modules
130
Virtual Ethernet Module (VEM)
128
Virtual Supervisor Module (VSM)
The VSMs can be placed in different physical data centers.
Note that the previous restrictions requiring the active-standby VSMs in a single physical data center do not apply anymore.
Hosts
128
Active VLANs and VXLANs across all VEMs
2048 VLANs and 2048 VXLANs (with a combined maximum of 4096)
MACs per VEM
32000
MACs per VLAN per VEM
4096
vEthernet interfaces per port profile
1024 (without static auto expand port binding)
Same as DVS maximum (with static auto expand port binding)
PVLAN
512
Distributed Virtual Switches (DVS) per vCenter with VMware vCloud Director (vCD)
32
Distributed Virtual Switches (DVS) per vCenter without VMware vCloud Director (vCD)
32
vCenter Server connections
1 per VSM HA Pair1
Maximum latency between VSMs and VEMs
100ms
Per DVS Per HostvEthernet interfaces
4096
3002
Port profiles
2048
—
System port profiles
32
32
Port channel
512
8
Physical trunks
512
—
Physical NICs
—
32
vEthernet trunks
256
8
ACL
128
163
ACEs per ACL
128
128
ACL instances
4096
300
NetFlow policies
32
8
NetFlow instances
256
32
SPAN/ERSPAN sessions
64
64
QoS policy map
128
16
QoS class map
1024
128
QoS instances
4096
300
Port security
2048
216
MultiCast groups
512
512
1 Only one connection to vCenter server is permitted at a time.
2 Upgrade from an earlier version of Cisco Nexus 1000V software to the current version of Cisco Nexus 1000V software displays the maximum vEth ports as 216. To get the current supported vEth limit, remove the host from DVS and add the host again.
3 This number can be exceeded if VEM has available memory.
Related Documentation
This section lists the documents used with the Cisco Nexus 1000V and available on Cisco.com at the following URL:
http://www.cisco.com/en/US/products/ps9902/tsd_products_support_series_home.html
General Information
Cisco Nexus 1000V Documentation Roadmap
Cisco Nexus 1000V Release Notes
Cisco Nexus 1000V Compatibility Information
Install and Upgrade
Cisco Nexus 1000V Installation and Upgrade Guide
Configuration Guides
Cisco Nexus 1000V High Availability and Redundancy Configuration Guide
Cisco Nexus 1000V Interface Configuration Guide
Cisco Nexus 1000V Layer 2 Switching Configuration Guide
Cisco Nexus 1000V License Configuration Guide
Cisco Nexus 1000V Network Segmentation Manager Configuration Guide
Cisco Nexus 1000V Port Profile Configuration Guide
Cisco Nexus 1000V Quality of Service Configuration Guide
Cisco Nexus 1000V REST API Plug-in Configuration Guide
Cisco Nexus 1000V Security Configuration Guide
Cisco Nexus 1000V System Management Configuration Guide
Cisco Nexus 1000V vCenter Plugin Configuration Guide
Cisco Nexus 1000V VXLAN Configuration Guide
Cisco Nexus 1000V vCenter Plugin Configuration Guide
Programming Guide
Cisco Nexus 1000V XML API User Guide
Reference Guides
Cisco Nexus 1000V Command Reference
Cisco Nexus 1000V MIB Quick Reference
Cisco Nexus 1000V Resource Availability Reference
Troubleshooting, Password Recovery, System Messages Guides
Cisco Nexus 1000V Troubleshooting Guide
Cisco Nexus 1000V Password Recovery Guide
Cisco NX-OS System Messages Reference
Virtual Services Appliance Documentation
The Cisco Nexus Virtual Services Appliance (VSA) documentation is available at
http://www.cisco.com/en/US/products/ps9902/tsd_products_support_series_home.html
Virtual Security Gateway Documentation
The Cisco Virtual Security Gateway documentation is available at
http://www.cisco.com/en/US/products/ps13095/tsd_products_support_series_home.html
Virtual Network Management Center
The Cisco Virtual Network Management Center documentation is available at
http://www.cisco.com/en/US/products/ps11213/tsd_products_support_series_home.html
Virtual Wide Area Application Services (vWAAS)
The Virtual Wide Area Application Services documentation is available at
http://www.cisco.com/en/US/products/ps6870/tsd_products_support_series_home.html
ASA 1000V Cloud Firewall
The ASA 1000V Cloud Firewall documentation is available at
http://www.cisco.com/en/US/products/ps12233/tsd_products_support_series_home.html
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see What's New in Cisco Product Documentation at: http://www.cisco.com/en/US/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 deliver content directly to your desktop using a reader application. The RSS feeds are a free service.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
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: 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)
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.
© 2013 Cisco Systems, Inc. All rights reserved.