Cisco Nexus 1000V Release Notes, Release 5.2(1)SV3(1.2)
Software Compatibility with VMware
Software Compatibility with CiscoNexus 1000V
Cisco Virtual Switch Update Manager
Deprecated and Removed Features
VSG Release 5.2(1)VSG2(1.2) Limitations
AVS Release 5.2(1)SV3(1.2) Limitations
VDP Release 5.2(1)SV3(1.2) Limitations
Configuration Container Names Must Be Unique
Single VMware Data Center Support
Cisco NX-OS Commands Might Differ from Cisco IOS
DHCP Not Supported for the Management IP
Copy Running-Config Startup-Config Command
SNMP User Accounts Must Be Reconfigured After an Upgrade
Obtaining Documentation and Submitting a Service Request
This document describes the features, limitations, and restrictions for the Cisco Nexus 1000V for VMware Release 5.2(1)SV3(1.2). It also explains how to find information about bugs. The following table lists the change history for this document.
Noted that scale limits for the Cisco Nexus 1000V Essential edition are half of the values of the Cisco Nexus 1000V Advanced edition. |
|
Added information about the access-class command in the Access Lists section. |
|
Added the SNMP User Accounts Must Be Reconfigured After an Upgrade section. |
|
Added the Deprecated and Removed Features section to note that vCenter plug-in support is deprecated. |
|
Added the ERSPAN section. |
This document includes the following sections:
The Cisco Nexus 1000V for VMware provides a distributed, Layer 2 virtual switch that extends across many virtualized hosts. The Cisco Nexus 1000V manages a data center defined by the vCenter Server. Each server in the data center is represented as a line card in the Cisco Nexus 1000V and can be managed as if it were a line card in a physical Cisco switch.
The servers that run the Cisco Nexus 1000V VSM and VEM must be in the VMware Hardware Compatibility list. This release of the Cisco Nexus 1000V supports vSphere 5.5, 5.1, and 5.0 release trains. For additional compatibility information, see the Cisco Nexus 1000V Compatibility Information.
Note The Cisco Nexus 1000V supports all virtual machine network adapter types that VMware vSphere supports. Refer to the VMware documentation when choosing a network adapter. For more information, see the VMware Knowledge Base article #1001805.
This release supports hitless upgrades from Release 4.2(1)SV2(1.1) and later. For more information, see the Cisco Nexus 1000V Software Upgrade Guide.
This section describes the new software features in Cisco Nexus 1000V 5.2(1)SV3(1.2).
You can use role-based access control list (RBACL) logging to monitor flows that affect specific RBACLs. The RBACLs can be configured with the optional log keyword in each of the access control entries (ACEs).
When you configure an option, statistics for each flow that match the RBACL permit or deny conditions that you enter are logged in the software.
The Virtual Station Interface (VSI) Discovery and Configuration Protocol (VDP) on the Cisco Nexus 1000V is part of the IEEE standard 802.1Qbg (Edge Virtual Bridging). VDP can detect and signal the presence of end hosts and define message exchanges with an adjacent VDP-capable bridge. You can now configure VDP on one or more VLANs.
This section describes the changed software features in Cisco Nexus 1000V Release 5.2(1)SV3(1.2).
Cisco Virtual Switch Update Manager (VSUM) Release 1.1 lets you install a Cisco Nexus 1000V switch by creating a new VSM or by using an existing VSM that is on a Cisco Nexus Cloud Services Platform (CSP). In the earlier release, you could install a Cisco Nexus 1000V switch only by creating a new VSM.
For more information, see the Cisco VSUM Release Notes.
Support of the vCenter plug-in is deprecated in this release. Cisco VSUM has replaced vCenter plug-in functionality.
This section describes the limitations and restrictions of the Cisco Nexus 1000V for VMware.
The following table lists the configuration scale limit information for the Cisco Nexus 1000V Advanced edition.
Note The scale limits for the Cisco Nexus 1000V Essential edition are half of the values stated in the following table.
In Release 5.2(1)SV3(1.2), when Cisco Virtual Security Gateway (VSG) solutions using version 5.2(1)VSG2(1.2) are deployed, the following scale limitations apply and supersede the scale numbers shown in Table 1 :
In Release 5.2(1)SV3(1.2), when AVS solutions are deployed, the following scale limitations apply and supersede the scale numbers shown in Table 1 :
In Release 5.2(1)SV3(1.2), when VDP solutions are deployed, the following scale limitations apply and supersede the scale numbers shown in Table 1 :
All Cisco Nexus 1000V VSM configuration containers—port profiles, bridge domains, ACLs, class maps, policy maps, and so on—must have unique names.
In releases earlier than 5.2(1)SV3(1.1) you could create two configuration containers (for example, two port profiles) with the same name but different case sensitivity; for example, vmotion and VMOTION.
In later releases, you cannot create two configuration containers (for example, two port profiles) with the same name but different case sensitivity. During an upgrade, one of the port profiles with a duplicate name is deleted, which moves the corresponding ports in vCenter into quarantined state.
For example, do not create bridge domains with the same name (one uppercase, one lowercase) that point to different segments. (See Example 1 and Example 2.)
The Cisco Nexus 1000V for VMware can be connected to a single VMware vCenter Server data center object. Note that this virtual data center can span multiple physical data centers.
Each VMware vCenter can support multiple Cisco Nexus 1000V VSMs per vCenter data center.
Implementing VDP on the Cisco Nexus 1000V has the following limitations and restrictions:
If the ERSPAN source and destination are in different subnets, and if the ERSPAN source is an L3 control VM kernel NIC attached to a Cisco Nexus 1000V VEM, you must enable proxy-ARP on the upstream switch.
If you do not enable proxy-ARP on the upstream switch (or router, if there is no default gateway), ERSPAN packets are not sent to the destination.
VMotion of VSM has the following limitations and restrictions:
For more information about VMotion of VSM, see the Cisco Nexus 1000V Software Installation Guide.
Port profiles have the following limitations and restrictions:
Note If there are any existing port profiles (created in earlier Cisco Nexus 1000V releases) with names that contain a forward slash (/), backslash (\), percent (%), or question mark (?), you can continue to use them in this release.
Only LACP offload to VEM is supported. Upgrades from earlier releases to this release change LACP to offload mode by default.
Be aware that the Cisco NX-OS CLI commands and modes might differ from those commands and modes used in the Cisco IOS software.
For information about CLI commands, see the Cisco Nexus 1000V Command Reference.
The Cisco Nexus 1000V for VMware forwarding logic is designed to prevent network loops; therefore, it does not use the Spanning Tree Protocol. Packets that are received from the network on any link connecting the host to the network are not forwarded back to the network by the Cisco Nexus 1000V.
The Cisco Discovery Protocol (CDP) is enabled globally by default.
CDP runs on all Cisco-manufactured equipment over the data link layer and does the following:
– CDP can discover up to 256 neighbors per port if the port is connected to a hub with 256 connections.
If you disable CDP globally, CDP is also disabled for all interfaces.
For more information about CDP, see the Cisco Nexus 1000V System Management Configuration Guide.
DHCP is not supported for the management IP. The management IP must be configured statically.
We recommend that you configure spanning-tree port type edge on upstream switches for faster convergence.
The following commands are available to use on Cisco upstream switch ports in interface configuration mode:
When the maximum transmission unit (MTU) is configured on an operationally up interface, the interface goes down and comes back up.
Supported MTU values vary according to underlying physical NIC capability.
When a VEM communicates with the Cisco VSG in Layer 3 mode, an additional header with 94 bytes is added to the original packet. You must set the MTU to a minimum of 1594 bytes to accommodate this extra header for any network interface through which the traffic passes between the Cisco Nexus 1000V and the Cisco VSG. These interfaces can include the uplink port profile, the proxy ARP router, or a virtual switch.
When you are using the copy running-config startup-config command, do not press the PrtScn key. If you do, the command aborts.
If you are upgrading from a release earlier than 5.2(1)SV3(1.1), the SNMP engine ID changes internally to a unique engine ID. You must reconfigure all SNMP user accounts to work with the new engine ID. Until the SNMP user accounts are reconfigured, all SNMPv3 queries fail. This restriction is associated with the defect CSCuo12696.
After an upgrade, the engine ID is shown as 128:0:0:9:3:2:0:12:0:0:0, as follows:
Complete the following steps to delete and recreate the username. Note that paswd123 is an example that represents the SNMP user password.
Step 2 Use one of the following options to recreate the username:
Step 3 Confirm that the engine ID has been updated, as follows:
Step 4 Verify that the engine ID is unique:
Use the Bug Search tool to search for a specific bug or to search for all bugs in a release.
Step 1 Go to http://tools.cisco.com/bugsearch.
Step 2 At the Log In screen, enter your registered Cisco.com username and password; then, click Log In. The Bug Search page opens.
Note If you do not have a Cisco.com username and password, you can register for them at http://tools.cisco.com/RPF/register/register.do.
Step 3 To search for a specific bug, enter the bug ID in the Search For field and press Return.
Step 4 To search for bugs in the current release:
a. In the Search For field, enter Cisco Nexus 1000V for VMware and press Return. (Leave the other fields empty.)
b. When the search results are displayed, use the filter tools to find the types of bugs you are looking for. You can search for bugs by modified date, status, severity, and so forth.
To export the results to a spreadsheet, click the Export Results to Excel link.
Table 5 lists the bug ID and description of a select number of resolved high-priority bugs in the Cisco Nexus 1000V for VMware.
The Cisco Management Information Base (MIB) list includes Cisco proprietary MIBs and many other Internet Engineering Task Force (IETF)-standard MIBs. These standard MIBs are defined in Requests for Comments (RFCs). To find specific MIB information, you must examine the Cisco proprietary MIB structure and related IETF-standard MIBs supported by the Cisco Nexus 1000V.
The MIB Support List is available at the following FTP site:
ftp://ftp.cisco.com/pub/mibs/supportlists/nexus1000v/Nexus1000VMIBSupportList.html
To provide technical feedback on this document or report an error or omission, please send your comments to:
The Cisco Nexus 1000V documentation is available at the following URL:
Cisco Nexus 1000V for VMware vSphere Documentation
Application Virtual Switch Documentation
Cisco Application Virtual Switch Documentation
ASA 1000V Cloud Firewall Documentation
Cisco ASA 1000V Cloud Firewall Documentation
Cloud Services Platform Documentation
Cisco Cloud Services Platform Documentation
Prime Network Services Controller Documentation
Cisco Prime Network Services Controller Documentation
Virtual Application Container Services Documentation
Cisco Virtual Application Container Services Documentation
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/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.