Table of Contents

n1000v_rn.fm

Cisco Nexus 1000V Release Notes, Release 4.2(1)SV2(1.1)

First Published: 2012-10-02

Release: NX-OS Release 4.2(1)SV2(1.1)

This document describes the features, limitations, and bugs for the Cisco Nexus 1000V Release 4.2(1)SV2(1.1) software. The following is the change history for this document.

Date

Description

2016-05-13

Moved CSCtt40944 to the “Resolved Bugs” section.

2013-08-01

Updated the “LACP” section and added the “Upstream Switch Ports” section.

2012-12-14

Updated the support limit for “Distributed Virtual Switches (DVS) per vCenter with VMware vCloud Director (vCD)” in Table 1.

2012-12-06

Added a note about a VEM upgrade when LACP is configured to the “Software Compatibility with VMware” section.

2012-10-02

Created release notes for Release 4.2(1)SV2(1.1). Added vCD 5.1 support.

Contents

This document includes the following sections:

- Introduction

- Software Compatibility with VMware

- Software Compatibility with Cisco Nexus 1000V

- New and Changed Information

- Limitations and Restrictions

- Bugs

- MIB Support

- Obtaining Documentation and Submitting a Service Request

Introduction

The Cisco Nexus 1000V 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 Cisco Nexus 1000V consists of the following components:

- Virtual Supervisor Module (VSM), which contains the Cisco CLI, configuration, and high-level features.

- Virtual Ethernet Module (VEM), which acts as a line card and runs in each virtualized server to handle packet forwarding and other localized functions.

Software Compatibility with VMware

.

Note When LACP is configured on the Cisco Nexus 1000V and the ESXi version is 4.1.0 or 5.1.0, a VEM upgrade to Cisco NX-OS Release 4.2(1)SV2.1(1) from any earlier release is not supported.

Note All virtual machine network adapter types that VMware vSphere supports are supported with the Cisco Nexus 1000V. Refer to the VMware documentation when choosing a network adapter. For more information, see the VMware Knowledge Base article #1001805.

Software Compatibility with Cisco Nexus 1000V

.

ISSU Upgrades

Performing an ISSU from Cisco Nexus 1000V Release 4.2(1)SV1(4a) or Release 4.2(1)SV1(4b) to Cisco Nexus 1000V Release 4.2(1)SV2(1.1) using ISO files is not supported. You must use kickstart and system files to perform an ISSU upgrade to Cisco Nexus 1000V Release 4.2(1)SV2(1.1).

New and Changed Information

This section describes new and changed features in Cisco Nexus 1000V Release 4.2(1)SV2(1.1).

Changed Software Features

Installer changes were made in Cisco Nexus 1000V Release 4.2(1)SV2(1.1).

Installer Enhancements

The Cisco Nexus 1000V Installer App is now a standalone Java application that can install the Cisco Nexus1000V VSM or VEM.

The Cisco Nexus 1000V Installer App supports a single pane for invoking the Cisco Nexus1000V VSM installer and VEM installer.

New Software Features

This section describes new software features in Cisco Nexus 1000V Release 4.2(1)SV2(1.1).

Release Support

This release supports VMware Release 5.1 and VMware vCloud Director 5.1.

Cross Data Center High Availability

This feature supports split active and standby Nexus 1000V Virtual Supervisor Modules (VSMs) across two data centers to implement cross-DC clusters and VM mobility while ensuring high availability.

DHCP Enhancements

Starting with Release 4.2(1)SV2(1.1), you can filter the traffic based on the source IP address only as opposed to filtering the traffic based on the IP-MAC address pair. The Cisco Nexus 1000V ignores the MAC address and validates only the source IP address of the traffic from the VMs. The new functionality applies only to static bindings; for dynamic bindings, a new MAC address updates the dynamic binding on the Cisco Nexus 1000V.

To enable source IP-based filtering on the Cisco Nexus 1000V switch, set the filter mode to ip filtering. The default filtering mode is ip-mac filtering.

Enhanced Installer App

This feature simplifies the entire installation process via a single pane of glass.

Enhanced Upgrade Process

Starting with Release 4.2(1)SV2(1.1), the upgrade process is simplified and flexible. You can schedule upgrades on a per-host basis, enabling an incremental upgrade even during a short maintenance window.

Enhanced Headless Mode

If a VEM loses the connection to its VSM, the Vmotions to that particular VEM are blocked. The VEM shows up in the VCenter Server as having a degraded (yellow) status.

Licensing Changes

Starting with Release 4.2(1)SV2(1.1), a tier-based licensing approach is adopted for the Cisco Nexus 1000V. The Cisco Nexus 1000V is shipped in two editions: Essential and Advanced. A new CLI command is provided to display the current switch edition and the other licensing information. In the two-tier licensing model supported with Release 4.2(1)SV2(1.1), the software image is the same for both editions. You can switch between the two editions at any time. The switch edition configuration is global. The entire switch (supervisor and all modules) is either in the Essential edition or the Advanced edition.

Essential Edition

When the Release 4.2(1)SV2(1.1) software is installed, the Essential edition is the default edition. When the switch is configured in the Essential edition, all features (other than the advanced features) are available for free for an unlimited time. No licenses are required to operate the Essential edition. The switch edition configuration is global and not per module. In Essential edition, all modules are automatically licensed. Use the svs switch edition command to move the switch from the Essential edition to the Advanced edition, and vice versa.

Advanced Edition

The switch will come up in the Advanced edition when it is upgraded from a pre-4.2(1)SV2(1.1) release. When the license expires, the switch does not move from the Advanced edition to the Essential edition automatically. You must use svs switch edition CLI command to downgrade to the Essential edition.The licenses are required only when the switch edition is configured as the Advanced edition.

The following features are available as advanced features that require licenses:

- Cisco TrustSec

- DHCP snooping

- Dynamic ARP inspection

- IP source guard

Use the feature cts command to configure Cisco TrustSec on the Cisco Nexus 1000V. Enable DHCP snooping, Dynamic ARP inspection, and IP source guard on the Cisco Nexus 1000V using the feature dhcp command. See the Cisco Nexus 1000V License Configuration Guide for more information on licensing.

Split-Brain Enhancements

The high availability mechanism on Cisco Nexus 1000V is enhanced to select the VSM to be rebooted during the split-brain resolution. The following parameters are used to select the VSM in order of their precedence:

- Module count: The number of modules attached to the VSM.

- vCenter status: The vCenter connectivity status.

- Last configuration time: The time when the last configuration is done on the VSM.

- Last active time: The time when the VSM becomes active.

When a VSM is rebooted, the accounting logs that are stored on the VSM are lost. Starting with Release 4.2(1)SV2(1.1), new CLI commands are supported to display the accounting logs that were backed up during the split-brain resolution. You can also check the redundancy traces that are stored on the local and remote VSMs. See the Cisco Nexus 1000V High Availability Configuration Guide for more information.

Support for Cisco TrustSec

The Cisco TrustSec security architecture builds secure networks by establishing clouds of trusted network devices. Each device in the cloud is authenticated by its neighbors. Communication on the links between devices in the cloud is secured with a combination of encryption, message integrity checks, and data-path replay protection mechanisms. Cisco TrustSec uses the device and user identification information acquired during authentication for classifying, or coloring, the packets as they enter the network. This packet classification is maintained by tagging packets on ingress to the Cisco TrustSec network so that they can be properly identified for the purpose of applying security and other policy criteria along the data path. The tag, also called the Security Group Tag (SGT), allows the network to enforce the access control policy by enabling the endpoint device to act upon the SGT to filter traffic.

vCenter Plug-In

This feature gives server administrators a networking view of the virtual network from within VMware vCenter.

vTracker

This feature gives network administrators VM-level and host-level visibility to the virtual and physical networks; for example, VM name and vMotion events.

Limitations and Restrictions

This section describes the Cisco Nexus 1000V limitations and restrictions.

Configuration Limits

lists the Cisco Nexus 1000V configuration limits.

Table 1 Configuration Limits for Cisco Nexus 1000V

Component

Supported Limits for a Single Cisco Nexus 1000V Deployment Spanning up to 2 Physical Data Centers

Maximum modules

66

Virtual Ethernet Module (VEM)

64

Virtual Supervisor Module (VSM)

The VSMs can be placed in different physical data centers.

Note The previous restrictions requiring the active-standby VSMs in a single physical data center no longer apply.

Hosts

64

Active VLANs or VXLANs across all VEMs

2048 (any combination of VLANs and VXLANs)

MACs per VEM

32,000

MACs per VLAN per VEM

4000

vEthernet interfaces per port profile

1024

PVLAN

512

Distributed Virtual Switches (DVS) per vCenter with VMware vCloud Director (vCD)

32

DVS per vCenter without vCD

32

vCenter Server connections

1 per VSM HA pair

Note Only one connection to the vCenter server is permitted at a time.

Maximum latency between VSMs and VEMs

100 ms

Component

Per DVS

Per Host

Virtual Service Domains (VSDs)

64

6

VSD interfaces

2048

216

vEthernet interfaces

2048

216

Port profiles

2048

—

System port profiles

32

32

Port channel

256

8

Physical trunks

512

—

Physical NICs

—

32

vEthernet trunks

256

8

ACL

128

16

Note This number can be exceeded if the VEM has available memory.

ACEs per ACL

128

128

Note This number can be exceeded if the VEM has available memory.

ACL instances

2048

256

NetFlow policies

32

8

NetFlow instances

256

32

SPAN/ERSPAN sessions

64

64

QoS policy map

128

128

QoS class map

1024

1024

QoS instances

2048

256

Port security

2048

216

Multicast groups

512

512

Single VMware Data Center Support

The Cisco Nexus 1000V can be connected to a single VMware vCenter Server data center object. Note that this virtual data center can span multiple physical data centers.

VMotion of VSM

VMotion of the VSM has the following limitations and restrictions:

- VMotion of a VSM is supported for both the active and standby VSM VMs. For high availability, we recommend that the active VSM and standby VSM reside on separate hosts.

- If you enable Distributed Resource Scheduler (DRS), you must use the VMware anti-affinity rules to ensure that the two virtual machines are never on the same host, and that a host failure cannot result in the loss of both the active and standby VSM.

- VMware VMotion does not complete when using an open virtual appliance (OVA) VSM deployment if the CD image is still mounted. To complete the VMotion, either click Edit Settings on the VM to disconnect the mounted CD image, or power off the VM. No functional impact results from this limitation.

- If you are adding one host in a DRS cluster that is using vSwitch to a VSM, you must move the remaining hosts in the DRS cluster to the VSM. Otherwise, the DRS logic does not work, the VMs that are deployed on the VEM could be moved to a host in the cluster that does not have a VEM, and the VMs lose network connectivity.

.

Access Lists

ACLs have the following limitations and restrictions.

Limitations:

- IPV6 ACL rules are not supported.

- VLAN-based ACLs (VACLs) are not supported.

- ACLs are not supported on port channels.

Restrictions:

- IP ACL rules do not support the following:

– fragments option

– addressgroup option

– portgroup option

– interface ranges

- Control VLAN traffic between the VSM and VEM does not go through ACL processing.

NetFlow

The NetFlow configuration has the following support, limitations, and restrictions:

- Layer 2 match fields are not supported.

- NetFlow Sampler is not supported.

- NetFlow Exporter format V9 is supported

- NetFlow Exporter format V5 is not supported.

- The multicast traffic type is not supported. Cache entries are created for multicast packets, but the packet/byte count does not reflect replicated packets.

- NetFlow is not supported on port channels.

The NetFlow cache table has the following limitation:

- Immediate and permanent cache types are not supported.

Note The cache size that is configured using the CLI defines the number of entries, not the size in bytes. The configured entries are allocated for each processor in the ESX host and the total memory allocated depends on the number of processors.

Port Security

Port security has the following support, limitations, and restrictions:

- Port security is enabled globally by default.

The feature/no feature port-security command is not supported.

- In response to a security violation, you can shut down the port.

- The port security violation actions that are supported on a secure port are Shutdown and Protect . The Restrict violation action is not supported.

- Port security is not supported on the PVLAN promiscuous ports.

Port Profiles

Port profiles have the following restrictions or limitations:

- There is a limit of 255 characters in a port-profile command attribute.

- We recommend that you save the configuration across reboots, which shortens the VSM bringup time.

- We recommend that if you are altering or removing a port channel, you migrate the interfaces that inherit the port channel port profile to a port profile with the desired configuration. Do not edit the original port channel port profile directly.

- If you attempt to remove a port profile that is in use (that is, one that has already been auto-assigned to an interface), the Cisco Nexus 1000V generates an error message and does not allow the removal.

- When you remove a port profile that is mapped to a VMware port group, the associated port group and settings within the vCenter Server are also removed.

- Policy names are not checked against the policy database when ACL/NetFlow policies are applied through the port profile. It is possible to apply a nonexistent policy.

Telnet Enabled by Default

The Telnet server is enabled by default.

.

SSH Support

Only SSH version 2 (SSHv2) is supported.

.

Cisco NX-OS Commands Might Differ from Cisco IOS

Be aware that the Cisco NX-OS CLI commands and modes might differ from those commands and modes used in the Cisco IOS software.

.

Layer 2 Switching: No Spanning Tree Protocol

The Cisco Nexus 1000V forwarding logic is designed to prevent network loops so it does not need to 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.

.

Cisco Discovery Protocol

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:

- Advertises information to all attached Cisco devices.

- Discovers and views information about those Cisco devices.

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

.

DHCP Not Supported for the Management IP

DHCP is not supported for the management IP. The management IP must be configured statically.

LACP

The Link Aggregation Control Protocol (LACP) is an IEEE standard protocol that aggregates Ethernet links into an EtherChannel.

The Cisco Nexus 1000V has the following restrictions for enabling LACP on ports carrying the control and packet VLANs:

Note These restrictions do not apply to other data ports using LACP.

- If LACP offload is disabled, at least two ports must be configured as part of LACP channel.

Note This restriction does not apply if LACP offload is enabled. You can check the LACP offload status by using the show lacp offload status command.

- The upstream switch ports must be configured in spanning-tree port type edge trunk mode.

Upstream Switch Ports

All upstream switch ports must be configured in spanning-tree port type edge trunk mode.

Without spanning-tree PortFast on upstream switch ports, it takes approximately 30 seconds to recover these ports on the upstream switch. Because these ports carry control and packet VLANs, the VSM loses connectivity to the VEM.

The following commands are available to use on Cisco upstream switch ports in interface configuration mode:

- spanning-tree portfast

- spanning-tree portfast trunk

- spanning-tree portfast edge trunk

DNS Resolution

The Cisco Nexus 1010 (1000V) cannot resolve a domain name or hostname to an IP address.

Interfaces

When the maximum transmission unit (MTU) is configured on an operationally up interface, the interface goes down and comes back up.

Layer 3 VSG

When a VEM communicates with 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.

VM Name Display Length Limitation

command—only VMs with names that are 21 characters or less are displayed correctly. Longer VM names might be truncated or have extra characters appended. Depending on the network adapter, the name length limitation varies. For example:

- The E1000 or VMXNET 2 network adapters allow 26-character names. At 27 characters, the word ‘.eth’ is appended to the VM name. With each addition to the VM name, a character is truncated from the word ‘.eth’. After 31 characters, the VM name is truncated.

- The VMXNET 3 network adapters allow 21-character names. At 22 characters, the word ‘ethernet’ is appended to the VM name. With each addition to the VM name, a character is truncated from the word ‘ethernet’. After 30 characters, the VM name is truncated.

Note This is a display issue with ESX Release 4.1 only. Use VM names of 21 characters or less to avoid this issue.

ISSU Upgrades

Performing an ISSU from Cisco Nexus 1000V Release 4.2(1)SV1(4) or Release 4.2(1)SV1(4a) to Cisco Nexus 1000V Release 4.2(1)SV2(1.1) using the ISO files is not supported. You must use the kickstart and the system files to perform an ISSU upgrade to Cisco Nexus 1000V Release 4.2(1)SV2(1.1).

Copy Running-Config Startup-Config Command

When running the copy running-config startup-config command, do not press the PrtScn key. If you do, the command will abort.

Error Messages Appear During ESX 4.1.0 Server Bootup

Vssnet-load error messages can occur during a classic ESX 4.1.0 server bootup or restart when the VEM is already installed. The issue occurs while booting up because the path environment variable is not set up correctly, and the system is not able to identify the VMware command. After the system boots up, it is set up correctly and so is the ESX 4.10 system. There is no functional impact of the error messages and they can be ignored.

Dynamic Entries Are Not Deleted for a Linux VM

On a Linux VM that has multiple adapters, a DHCP release packet is sent from an incorrect interface (because of OS functionality) and the DHCP release packet is dropped. As a result, the binding entry is not deleted. This issue is a Linux issue where the packets from all interfaces go out of one interface (which is the default interface). To avoid this issue, put the interfaces in different subnets and make sure that the default gateway for each interface is set.

Source Filter TX VLANs Are Missing After the VSM Restarts

When a SPAN (erspan-source) session is created and the source interface is configured as a port channel and PVLAN Promiscuous access is programmed, the filter RX is not configured and the configured programmed filter TX is not persistent on VSM reload.

To work around this issue, configure all the primary and secondary VLANs as filter VLANs while using the port channel with PVLAN Promiscuous access as the source interface.

Default SSH Inactive Session Timeout

command to explicitly configure the inactive session timeout limit.

Queueing Policy Cannot Be Changed in Flexible Upgrade Setup

Queuing is valid starting from Cisco NX-OS Release 4.2(1)SV1(51). Any queueing configuration that exists on the VSM in an earlier release will stop working. All port profiles that have a queueing configuration cannot be used. If a port is down, it should be moved to a profile without QoS queueing.

Clear QoS Statistics Fails on the VSM

When a policy map of type “queuing” has a class map of type “match-any” without any match criteria, and is applied on an interface, a resource pool is not created for that specific class ID. As a result, the collection of statistics fails and no data is sent back to the VSM. To work around this issue, add a match criteria on the empty class map.

Bugs

This section includes the following topics:

- Open Bugs

- Resolved Bugs

Open Bugs

The following are descriptions of bugs in Cisco Nexus 1000V Release 4.2(1)SV2(1.1). The ID links you into the Cisco Bug Search Tool.

The bugs are listed in the following categories:

- Platform, Infrastructure, Ports, Port Channel, and Port Profiles

- Quality of Service

- Features

- VMware

Platform, Infrastructure, Ports, Port Channel, and Port Profiles

ID

Headline

Need to send traffic from the destination VM to learn the vns-binding.

The Cisco Nexus 1000V cannot support more than 245 ports (physical and virtual) per VEM.

Not able to migrate VC/VSM and normal VM when adding host to DVS.

CSCtj70071

SNMP V3 traps are not getting generated.

CSCtn62514

LACP offload configuration is not persisting in stateless mode.

CSCtq04886

Eth_port_sec crash occurs during migration in VC with interface override in VSM.

CSCtq92519

CDP does not work for certain NIC cards without VLAN 1 allowed.

CSCtr34519

Continuous SNMP polling causes high CPU usage.

CSCtr36181

Integrate Apache with netstack.

CSCtr55311

Legacy LACP takes 30 minutes to come up after a link flap.

CSCts24105

command configuration is not working.

CSCts50066

Post module flap violated port is secured and the secured port is violated.

CSCtt07479

command reserves more than the default ports.

CSCtt17073

A port profile via VCD fails when done immediately after a switchover.

CSCtt24735

Editing a port profile fails with the error message “ERROR: unknown error.”

CSCtz04587

Reloading the VSM takes 12 minutes for modules to come online and vEthernet interfaces to come up

CSCtu10144

A virtual Ethernet interface as trunk has pinning issue in MN ESX hosts.

CSCtu17512

The Cisco Nexus 1000V to vShield Manager connection is down after release of VCD, DB, VSM.

Note Only applicable with VMware vCloud Director 1.5.1 and vShield Manager 5.0.1.

CSCtw93579

Active VSMs CPU utilization is more than 50% when there are 512 groups.

CSCtw96064

command does not have output related to DHCP snooping.

CSCtx06864

A native VLAN configured on the interface port channel is not programmed on the VEM.

CSCtx30435

After upgrading the VEM to Cisco NX-OS Release 4.2(1)SV1(5.1), two Cisco VIBs are installed.

CSCty59712

If you add a primary PVLAN as the SPAN/ERSPAN source, its promiscuous trunk members are not added to the SPAN session.

CSCua00940

PPM does not perform configuration checks when you configure a PVLAN in an offline port-profile mode.

CSCua02145

“SYSMGR_EXITCODE_FAILURE_NOCALLHOME” error message received while upgrading with ISO images from Release 4.2(1)SV1(4) or 4.2(1)SV1(4a) to Release 4.2(1)SV1(5.2).

CSCua06287

Incorrect mapping for ethernet port profile with PVLAN configuration is displayed in the running configuration.

CSCua11227

Cannot copy the running configuration from the TFTP server to the current running configuration.

CSCua12342

A Link Aggregation Control Protocol (LACP) port channel member port goes to the suspended state when the port is newly added to the LACP port channel, or the port is removed and re-added to the LACP port channel.

CSCua12592

Password validity is not checked when installing a VSM using an OVA installation.

CSCua16092

If you add a PVLAN promiscuous trunk port channel or Ethernet interface as the SPAN/ERSPAN source, some of the VLANs allowed on the port might not be spanned.

CSCua30287

An error occurs while trying to override the PVLAN mapping in the child port profile.

CSCua59482

Traffic is being redirected to the incorrect VSG.

CSCua73549

Modules are not reattached after a VMKnic MAC address change in Layer 3 mode.

CSCub23161

VCD does not display relevant error descriptions for error codes.

CSCub25986

NSM should fix the Cisco Nexus 1000V feature limitation issue.

CSCub33444

Powering up a single VM configures all vApp networks.

CSCub69289

Veths mapped to the port profiles are not counted in the show resource-availability monitor command.

CSCub79332

The server IP address becomes 0.0.0.0 for a MN stateless host.

CSCub90212

SPAN sources are deleted on the VEM output while adding the source interfaces. Duplicated by CSCtz82836.

CSCuc58678

The installer displays an error when a host with multiple VMKnics in the same VLAN is migrated.

CSCuc49513

command output has the graphing backwards.

CSCuc63801

Traffic loss occurs after the VSM reloads if PSEC is restricted and the DSM bit is set.

Quality of Service

ID

Headline

CSCtl00949

command is causing inherit to fail.

CSCtq34938

Applying policy fails sharing ACL between two class-maps of same policy.

CSCtu36119

QoS marking limitation in VCD environment.

Features

ID

Headline

PSEC with multiple MAC addresses and PVLAN not supported.

Port migration with switchover causing ports to go to “No port-profile.”

CSCtq89961

Snooping does not get applied on sec VLANs if executed in different order

CSCtr06833

Split brain causes pending ACL/QoS transactions into err-disabled.

CSCtr09746

Interface configuration fails when veths are nonparticipating due to unreachable module.

CSCub44964

A RADIUS AAA error occurs when feature CTS is enabled and there is a switchover.

VMware

ID

Headline

Removing host with Intel Oplin from DVS causes all ports to reset.

After an ESX host exception, the port group configuration on PNIC is changed.

Fully qualified domain name/user with port-profile visibility fails.

Port-profile visibility feature is not able to update permissions.

Improper sync with vCenter when port-profile names have special characters.

A VEM upgrade fails when the scratch space is a network file system.

CSCtt00444

After unregistering Cisco Nexus 1000V on Vshield, the alert timer runs.

CSCty78076

VEM upgrade error occurs when using VMware Update Manager.

CSCua30356

An existing vAPP cannot be powered down, and a new vAPP cannot be deployed.

CSCua40492

When the VEM is disconnected from the VSM (headless mode), the maximum number of vEthernet interfaces limit cannot be connected.

When VIBs are removed from ESX 4.1 hosts in maintenance mode, the hosts return to maintenance mode after reboot.

CSCua78262

The incorrect release description name and release note URL is displayed with the ESX/ESXi 4.1.0 offline bundle.

CSCub56123

Wrong message for VC user id and Password.

CSCub90212

Span sources gets deleted on VEM output while adding source intfs.

CSCuc71793

Ports go to error disabled state during ACL or QoS Commit Errors.

CSCuc75398

App fail power on with insufficient resource error.

CSCuc80063

IGMP process failing to read PVLAN association.

Resolved Bugs

The following are descriptions of bugs that are resolved in Cisco Nexus 1000V Release 4.2(1)SV2(1.1). The ID links you into the Cisco Bug Search Tool.

ID

Headline

CSCtq34432

command with the wrong policy name.

CSCtq34977

Interface in “NoPortProfile” state on mode changes from LACP to MAC pinning.

CSCtt40944

In a PVLAN, all mappings are removed when a single mapping is removed.

CSCtw50899

command.

CSCtw56889

Cisco Nexus 1000V does not recompute the UDP checksum when option 82 is inserted.

CSCtw69713

A module does not come up if the lowest numbered vmnic on Cisco Nexus 1000V is down.

CSCtw72196

Queues are not created when adding a class map in a policy map that has no cl.

CSCtx02138

ERSPAN supports an MTU larger than 1500 bytes.

CSCtx03892

A migration to Cisco Nexus 1000V multicast with 224.0.0.1 address stopped working.

CSCtx32992

Multicast drops count as vEth output drops.

CSCtx39449

Module flaps and disconnection of svs connection observed.

CSCtx41516

command on a vEthernet interface.

CSCtz12186

command does not show the status of http and https.

CSCtz57199

N1K port-channel loadbalance is not consistent on VEM.

CSCua92452

A VMware critical failure is seen when unloading VEM modules during VEM Upgrade with VEM having L3 vmknic Control Interface with QoS and ACL configurations.

CSCua95040

There is an issue with PVLAN Promiscuous (access) PC and SPAN.

CSCub22714

NSMGR-network create failed with error.

CSCub36957

The VEM does not send a heartbeat when processing a large amount of Layer 2 broadcasts.

MIB Support

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

The MIB Support List is available at the following FTP site:

Obtaining Documentation and Submitting a Service Request

.

. RSS feeds are a free service.

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)

Internet Protocol (IP) addresses used in this document are for illustration only. Examples, command display output, and figures are for illustration only. If an actual IP address appears in this document, it is coincidental.

© 2012–2016 Cisco Systems, Inc. All rights reserved.