Cisco Nexus1000V for Microsoft Hyper-V Release Notes, Release 4.2(1)SV1(4)

Available Languages

Download Options

  • PDF     (528.1 KB)
    View with Adobe Reader on a variety of devices
Updated:February 2, 2015

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Table of Contents

Cisco Nexus 1000V Release Notes, Release 4.2(1) SV1(4)

Contents

Introduction

Software Compatibility

Software Compatibility with VMware

Software Compatibility with Cisco Nexus 1000V

New and Changed Information

Changed Software Features

Installer Application

Disabling HTTP Server

Feature Command

Port Profile Changes

Port Channel Changes

Scalability Limits

New Software Features

vPath Features

Pre-Upgrade Script

Upgrade Application

Restricting the Visibility of Port Profiles

LACP Offload

SPAN and ERSPAN with Port Profiles

Hardware iSCSI Multipathing

Class-Based Weighted Fair Queueing

Network State Tracking for vPC-HM

DHCP Option 82

ACLs on Management Interface

Ephemeral Port-Binding Type

Limitations and Restrictions

Configuration Limits

Single Data Center Supported

vMotion of VSM

VMware Lab Manager

Upgrades

Access Lists

NetFlow

Port Security

Port Profiles

Telnet Enabled by Default

SSH Support

Cisco NX-OS Commands May Differ from Cisco IOS

Layer 2 Switching

No Spanning Tree Protocol

Cisco Discovery Protocol

DHCP Not Supported for the Management IP

LACP

Upstream Switch Ports

DNS Resolution

Interfaces

Caveats

Open Caveats

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

Quality of Service

Features

VMware

Resolved Caveats

MIB Support

Available Documents

Cisco Nexus 1000V Release Notes, Release 4.2(1) SV1(4)

Updated: March 21, 2014

OL-22822-01-G0

This document describes the features, limitations, and caveats for the Cisco Nexus 1000V Release 4.2(1)SV1(4) software. Use this document in combination with documents listed in the “Obtaining Documentation and Submitting a Service Request” section. The following is the change history for this document.

 

Part Number
Revision
Date
Description

OL-22822-01

G0

8/2/13

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

OL-22822-01

F0

7/7/11

Revisions to Open Caveats, Resolved Caveats, and Limitations and Restrictions sections per Bug ID CSCtn16260.

OL-22822-01

E0

4/19/11

Added DNS Resolution to the Limitations and Restrictions section.

OL-22822-01

D0

3/7/11

Added CSCtn70031 to the Platform, Infrastructure, Ports, Port Channel, and Port Profiles section of Open Caveats.

OL-22822-01

C0

2/15/11

Added CSCtk61785 to the Features section of Open Caveats.

OL-22822-01

B0

2/9/11

Added section on Pre-Upgrade Script and modified Open Caveats and Resolved Caveats tables.

OL-22822-01

A0

1/31/11

Created release notes for Release 4.2(1)SV1(4).

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 Cisco Nexus 1000V and can be managed as if it were a line card in a physical Cisco switch.

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

This section includes the following topics:

Software Compatibility with VMware

The servers that run the Cisco Nexus 1000V VSM and VEM must be in the VMware Hardware Compatibility list. This release of Cisco Nexus 1000V supports both ESX 4.0 and ESX 4.1 release trains. For additional compatibility information, see the Cisco Nexus 1000V Compatibility Information, Release 4.2(1)SV1(4) .

Software Compatibility with Cisco Nexus 1000V

This release supports hitless upgrades from Release 4.0(4)SV1(3a) and later releases. Upgrades are supported from 4.0(4)SV1(3) and earlier releases. For additional information, see the Cisco Nexus 1000V Software Upgrade Guide, Release 4.2(1)SV1(4) .

New and Changed Information

This section provides the following information about this release:

Changed Software Features

The following software features were changed in this release:

Installer Application

The Installer Application GUI for setting up an initial Cisco Nexus 1000V deployment is enhanced to include the following:

  • New Layer 3 connectivity configuration option.
  • New HA (primary/secondary) deployment options.
  • New configuration file option to expedite the Installer Application usage.

For more information, see the Cisco Nexus 1000V Getting Started Guide, Release 4.2(1)SV1(4) .

Disabling HTTP Server

For security purposes, you can now disable the HTTP server which is embedded in the Virtual Supervisor Module (VSM). When using the VMWare Update Manager (VUM) , you need to enable the HTTP server while doing the upgrade. After the upgrade has completed, you have the option of disabling the HTTP server. For more information, see the Cisco Nexus 1000V Security Configuration Guide, Release 4.2(1)SV1(4) .

Feature Command

To enable features like DHCP, HTTPS, Link Aggregation Protocol (LACP), NetFlow, Port-Profile-Roles, Private VLANs (PVLANs), Secure Shell (SSH), TACACS, or Telnet, the feature feature_name command should be executed first.

If any of the features were configured before upgrading to Release 4.2(1)SV1(4), they will be automatically enabled during the upgrade process.

Port Profile Changes

The Port Profile Manager for the Cisco Nexus 1000V is enhanced to perform the following:

  • Port profiles are inherited onto interfaces atomically

– Either all the commands within the port profile are applied successfully or the inherit process is marked as a failure.

  • If the inherit process fails, the interfaces inheriting that port profile are quarantined.

– If an update of a port profile fails, the port profile and its inheriting interfaces roll back to the last known good configuration.

  • When an interface is quarantined, it is put into a shutdown state and requires manual intervention to reconcile the port profile attributes with the target interfaces.
  • Further CLI support for reverting child port profile and interface overrides to port profile defaults.
  • Some commands that were previously uninheritable are now inheritable.

For more information, see the Cisco Nexus 1000V Port Profile Configuration Guide, Release 4.2(1)SV1(4) .

Port Channel Changes

The channel-group id mode { on | active | passive } command under the Ethernet interface configuration mode is deprecated. Instead, you need to use the channel-group auto mode { on | active | passive } command in the uplink port profile used by Ethernet interfaces.

For more information, see the Cisco Nexus 1000V Interface Configuration Guide, Release 4.2(1)SV1(4) .

Scalability Limits

Scalability limits for multiple features have been increased in this release; refer to the “Configuration Limits” section for updated limits.

vPath Features

Cisco vPath plays an important role in providing flexible and scalable virtual network services architecture. The main components of this architecture are vPath and the Virtual Service Node (VSN) which provides the network service. The first instantiation of VSN is the Virtual Security Gateway (VSG).

Specifically, the Cisco vPath architecture provides:

  • Intelligent Traffic Steering

– Redirects traffic from the server requesting network service to the VSN

– Extends port profile to include the network service profile

  • Flexible Deployment

– Each VSN can serve multiple physical servers

– VSN can be hosted on a separate or dedicated server

  • Network Service Acceleration

– Network Service Decision Caching: Cisco Nexus 1000V remembers the network service policy from prior traffic reducing traffic steering

– Performance of virtual network services can be accelerated through enforcement in the hypervisor kernel

Pre-Upgrade Script

The upgrade procedure for Release 4.2(1)SV1(4) has changed. You must run the Pre-Upgrade Script prior to beginning the upgrade. Failing to run the Pre-Upgrade Script or Pre-Upgrade App could result in traffic disruption and might place your system in an unusable state.

Upgrade Application

An upgrade application has been added for VSM and VEM upgrades. For more information, see the Cisco Nexus 1000V Software Upgrade Guide, Release 4.2(1)SV1(4) .

Restricting the Visibility of Port Profiles

You can now restrict which vCenter Server users or user groups have visibility into specific port groups on the Cisco Nexus 1000V. For more information, see the Cisco Nexus 1000V Port Profile Configuration Guide, Release 4.2(1)SV1(4) .

LACP Offload

You can offload operation of the LACP protocol from the VSM to the VEMs to prevent a situation where the VSM cannot negotiate LACP with the upstream switch when the VEM is disconnected from the VSM (referred to as headless mode). VEM management of LACP allows LACP to re-establish port channels after the reboot of a headless VEM.

For more information, see the Cisco Nexus 1000V Interface Configuration Guide, Release 4.2(1)SV1(4) .

SPAN and ERSPAN with Port Profiles

Port profiles can be used as a source and destination for SPAN and ERSPAN monitored traffic. For more information, see the Cisco Nexus 1000V System Management Configuration Guide, Release 4.2(1)SV1(4) .

Hardware iSCSI Multipathing

A hardware adapter is now supported for iSCSI multipathing. For more information, see the Cisco Nexus 1000V System Management Configuration Guide, Release 4.2(1)SV1(4) .

Class-Based Weighted Fair Queueing

Class-Based Weighted Fair Queueing (CBWFQ) is a network queuing technique that allows the user to configure custom traffic classes based on various criteria. Each of these classes can be assigned a share of the available bandwidth for a particular link. Queuing is performed on the outbound direction of a physical link, with each class having its own queue and specific bandwidth reservation value. For more information, see the Cisco Nexus 1000V Quality of Service Configuration Guide, Release 4.2(1)SV1(4) .

Network State Tracking for vPC-HM

Network state tracking allows you to pinpoint link failures on a port channel configured for vPC-HM. For more information, see the Cisco Nexus 1000V Interface Configuration Guide, Release 4.2(1)SV1(4) .

DHCP Option 82

This release supports DHCP option 82 with remote-id (VSM control interface MAC) and circuit-id (vethernet port name) attributes, which could be used as matching criteria for the IP address allocation on a DHCP server.

ACLs on Management Interface

The management interface supports IPv4 ACLs that provide management interface security.

Ephemeral Port-Binding Type

This release supports setting the port-binding type within a port profile. When the port-binding type is set to ephemeral, a new DVPortID is allocation for the port every time a virtual machine is powered on. The DVPortID is released when the virtual machine is powered off.

For more information, see the Cisco Nexus 1000V Port Profile Configuration Guide, Release 4.2(1)SV1(4) .

Limitations and Restrictions

The Cisco Nexus 1000V has the following limitations and restrictions:

Configuration Limits

Table 1 shows the Cisco Nexus 1000V configuration limits:

 

Table 1 Configuration Limits for Cisco Nexus 1000V

Component
Supported Limit

Maximum Modules

66

Virtual Ethernet (VEM)

64

Virtual Supervisor (VSM)

2

Data Center per VSM

1

Active VLANs across all VEMs

2048 (2K)

MACs per VEM

16000 (16K)

MACs per VLAN per VEM

4000 (4K)

vEthernet interfaces per port profile - static binding type

1024 (1K)

PVLAN

512

vCenter Server connections

1 per VSM 1

Characters per port-profile attribute

255

Distributed Virtual Switches (DVS) per vCenter

12
Per DVS
Per Host

Virtual Service Domains (VSDs)

64

6

VSD interfaces

2048

214

vEthernet interfaces

2K

216

Port profiles

2048

—

System port profiles

32

32

Port channels

256

8

Physical NICs/trunks

512

32

vEthernet trunks

256

8

ACLs

128

162

ACEs per ACL

128

16 2

ACL Interfaces

2048

256

NetFlow policies

32

8

NetFlow interfaces

256

32

SPAN/ERSPAN sessions

64

64

QoS policy maps

128

16

QoS class maps

1024

128

QoS interfaces

2048

256

Port security

2000

216

MultiCast groups

512

512

1.Only one connection to vCenter Server is permitted at a time.

2.This number can be exceeded if VEM has available memory.

Single Data Center Supported

The Cisco Nexus 1000V currently supports a single data center. The VSM cannot be deployed across more than one data center.

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), then 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 VEM, and the VMs lose network connectivity.

For more information about vMotion of VSM, see the Cisco Nexus 1000V Software Installation Guide, Release 4.2(1)SV1(4) .

VMware Lab Manager

VMware Lab Manager does not support using the Cisco Nexus 1000V.

Upgrades

Upgrading the software has the following limitations and restrictions:

  • The upgrade procedure to Release 4.2(1)SV1(4) has changed depending on the version you are upgrading from.
  • Unlike previous upgrades, disruption free upgrades from Release 4.0(4)SV1(3) and later to Release 4.2(1)SV1(4) require the VEMs to be upgraded prior to upgrading the VSM.
  • VEM upgrade to Release 4.2(1)SV1(4) requires a minimum ESX/ESXi version of 4.0 Update 1 Patch 04 or later.
  • VEM Upgrade using VMware Update Manager (VUM) requires vCenter Update 1, VUM Patch 2 or later.

For more information about VMware compatibility, see the Cisco Nexus 1000V Compatibility Information, Release 4.2(1)SV1(4) .

For more information about upgrades, see the Cisco Nexus 1000V Software Upgrade Guide, Release 4.2(1)SV1(4) .

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 will shorten the VSM bringup time.
  • We recommend that if you are altering or removing a port channel, you should migrate the interfaces that inherit the port channel port profile should migrate to a port profile with the desired configuration, rather than editing 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.

For more information about Telnet, see the Cisco Nexus 1000V Security Configuration Guide, Release 4.2(1)SV1(4) .

SSH Support

Only SSH version 2 (SSHv2) is supported.

For more information, see the Cisco Nexus 1000V Security Configuration Guide, Release 4.2(1)SV1(4) .

Cisco NX-OS Commands May 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.

For information about CLI commands, see the Cisco Nexus 1000V Command Reference, Release 4.2(1)SV1(4) .

For more information about the CLI command modes, see the Cisco Nexus 1000V Getting Started Guide, Release 4.2(1)SV1(4)

Layer 2 Switching

This section lists the Layer 2 switching limitations and restrictions and includes the following topics:

For more information about Layer 2 switching, see the Cisco Nexus 1000V Layer 2 Switching Configuration Guide, Release 4.2(1)SV1(4) .

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, then CDP is also disabled for all interfaces.

For more information about CDP, see the Cisco Nexus 1000V System Management Configuration Guide, Release 4.2(1)SV1(4) .

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.

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 is not applicable if LACP offload is enabled. You can check the LACP offload status using the show lacp offload status command.

  • The upstream switch ports must be configured in spanning-tree port type edge trunk mode. For more information about this restriction, see the “Upstream Switch Ports” section.

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 are carrying control and packet VLANs, 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.

Caveats

This section includes the following topics:

Open Caveats

The following are descriptions of the caveats in Cisco Nexus 1000V Release 4.2(1)SV1(4). The ID links you into the Cisco Bug Toolkit.

The caveats are listed in the following categories:

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

 

ID
Open Caveat Headline

1.

CSCti39155

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

2.

CSCti85986

Cisco Nexus 1000Vcannot support more than 245 port (physical + virtual) per VEM.

3.

CSCti88131

VSM process reloads.

4.

CSCti98977

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

5.

CSCtj73683

Stuck module FSM causes continuous VEM flap.

6.

CSCtk12886

VEM sitting before active VSM keeps flapping.

7.

CSCtk19017

Back-to-back clear counters (in < 35s) can move active port to inactive state.

8.

CSCtk34637

Owner field missing for Ethernet ports in show port-profile virtual usage command.

9.

CSCtk36277

ARP reply from VSM is going on cntrl and mgmt.

10.

CSCtk36394

Only system VLANs programmed on PC after rapid LACP member flaps.

11.

CSCtk58968

Module does not attach after mode change from access to trunk.

12.

CSCtk59886

MTU not getting set after port channel is up.

13.

CSCtk61730

Incorrect iSCSI multipathing configuration causes module flap or vMotion failure.

14.

CSCtk65237

VEM not able to attach with two standalone uplinks.

15.

CSCtk67553

Ethernet port goes to admin down state while changing port profiles.

16.

CSCtk70131

VPC subgroup manual comes up though subgroup IDs are not configured.

17.

CSCtk82033

Traffic stops on upgrade when PLAN configuration under port channel.

18.

CSCtk94380

vEthernets going down and auto-deleted on switchover with port profile migration.

19.

CSC tl06194

UCS Blade Oplin adapter comes up with timing issue during Fl reboot.

20.

CSCtl 12586

After VIB upgrade, some of the palo NICs go into INIT state on Fl.

21.

CSCtl46979

MTU not getting set in VEM when inherited from a parent system port profile.

22.

CSCtl51406

After upgrade, interface is no longer shut down.

23.

CSCtl75073

The no channel-group command displays the following:
ERROR:No profile matching given profile name.

24.

CSCtn70031

DPA select loop not processing timers under heavy traffic.

Quality of Service

 

ID
Open Caveat Headline

1.

CSCtl12963

QoS policy on port channel is not getting updated when percentage policer is used.

2.

CSCtl44096

Queue-limit parameter for QoS queueing is not supported.

3.

CSCtl67678

Queueing not programmed on flapping Ethernet port not in a port channel.

4.

CSCtl70759

Addition of new NIC to port-channel fails if profile has queueing policy.

5.

CSCtl80191

Change in queueing parameters while VEM is offline does not take effect.

Features

 

ID
Open Caveat Headline

1.

CSCti32816

Multicast counters increment even after shutting the vethernet interface.

2.

CSCtj32577

Powering on large number of VMs or mass migration of port-profiles fails with acl/qos.

3.

CSCtk12280

Static/secured MAC address not being learned in the MAC table.

4.

CSCtk59233

GUI installer creates uplink profiles with static port channels.

5.

CSCtk61785

Trap types entity_module_inserted and entity_module_removed do not generate traps.

6.

CSCtk62416

SPAN session not going down when last source/destination goes down.

7.

CSCtk65252

PSEC with multiple MAC addresses and PVLAN not supported.

8.

CSCtk96773

The no feature private-vlan command does not remove switchport mode private vlan.

9.

CSCtl84889

Unable to span TX packets when source port-profile has port-channel configuration.

10.

CSCtn21667

PLAN trunk mapping only supports 128.

VMware

 

ID
Open Caveat Headline

1.

CSCtf97549

VSM-VC communication lost.

2.

CSCti34737

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

3.

CSCtj21289

PSOD when MTU values are changed inside port profile while traffic is flowing.

4.

CSCtk02322

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

5.

CSCtk07337

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

6.

CSCtk10837

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

7.

CSCtk53802

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

Resolved Caveats

The following are descriptions of caveats that were resolved in Cisco Nexus 1000V Release 4.2(1)SV1(4). The ID links you into the Cisco Bug Toolkit.

 

ID
Resolved Caveat Headline

1.

CSCta09184

The show policy-map and show class-map commands are not compatible with XML API.

2.

CSCta63359

Show interface show 10M when using Virtual Connect.

3.

CSCtd08705

Port channel packets on VEM needs to be corrected.

4.

CSCte19534

Show interface counters shows large numbers.

5.

CSCte36467

Support for ethanalyzer on Cisco Nexus 1000V

6.

CSCte55714

Unable to change the service port action from forward to drop.

7.

CSCtf06727

Current nightly image unable to dump netstack core file.

8.

CSCtf51187

VEM does not size VLAN bitmaps to be as many as system profiles.

9.

CSCtf53780

Syslogs during vem upgrade sequence to clarify/remind user

10.

CSCtf94335

IP ACLs on mgmt interface

11.

CSCtg03760

Active VLANs on VSM programmed on VEM - post link flap.

12.

CSCtg06894

Upgrade to software Release 4.0(4)SV1(3) may fail if you load Release 4.0(4)SV1(2) first immediately followed by Release 4.0(4)SV1(3).

13.

CSCtg11898

BL:Ethpm in erroneous loop causes module to flap continuously.

14.

CSCtg14360

Connection state of multiple veths out of sync with VEM.

15.

CSCtg22241

VSM interfaces down on standby VSM VM NICs flap.

16.

CSCtg45689

ISSU changes for Cisco Nexus 1000V

17.

CSCtg46514

LACP channel not formed during shut and no shut on upstream switch.

18.

CSCtg49230

CPPA:Mgmt IP info of VSB missing in cppamgr CLI output

19.

CSCtg82051

SNMP polling for certain MIBs may time out on Cisco Nexus 1000V.

20.

CSCtg97281

IGMPv2 leave causes members in other hosts to be removed.

21.

CSCth06324

feature http-server /no feature http-server

22.

CSCth13652

1000v NetFlow SysUptime decimal off by a few places

23.

CSCth14223

Av1/BL:HA: Repetitive GARP should be sent out on s/o from Stb to Act

24.

CSCth21824

The show module command displays wrong IP address.

25.

CSCth27405

Disable license manager in CPPA.

26.

CSCth30738

Memory corrupted during Layer 3 Control setup with VLAN 1.

27.

CSCth31100

Ethernet interfaces are not formed when module is attached.

28.

CSCth32758

show running-config output varies between successive runs.

29.

CSCth46091

VSM is not receiving vMotion event during VEM migration.

30.

CSCth76634

LACP member port goes into suspended state after VSM reload.

31.

CSCti40301

Nexus 1010 standby VSB not provisioned if description used on primary.

32.

CSCti47884

VPC-HM Mac-pinning shows LACP = Y under "vemcmd show pc" output

33.

CSCti56196

Excessive "WARNING: n1kv: sf_netif_port_update" log messages in vmkernel

34.

CSCti68109

Content missing from HA and Redundancy Configuration Guide

35.

CSCti71155

svs mode l3 not applicable on Cisco Nexus 1010.

36.

CSCti90320

Unwanted commands in CPPA mgr.

37.

CSCtj17451

If a virtual machine sends a 802.1Q packet on a virtual Ethernet port that has been configured as an access port, the server with this virtual machine will crash.

38.

CSCtj24662

Secondary VSM crashed with error message "Couldn't open shared segment"

39.

CSCtj45990

Cisco Nexus 1000V - VEMs unable to retrieve license due to busy license svc.

40.

CSCtj60608

write erase on Cisco Nexus 1010 should set Cisco Nexus 1010 to factory default.

41.

CSCtj62291

Supervisor reloads upon show vlan command.

42.

CSCtj89188

snmpwalk crashes snmpd then vim

43.

CSCtk01245

VSM should reject VLAN on multiple uplink port profiles

44.

CSCtk69035

The show vlan private-vlan command causes "Service not responding" error.

45.

CSCtl08089

Virtual Ethernet Module unable to recover from broadcast storm created by other parts of the network.

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

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

ftp://ftp.cisco.com/pub/mibs/supportlists/nexus1000v/Nexus1000VMIBSupportList.html

Available Documents

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

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s New in Cisco Product Documentation , which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.

This document is to be used in conjunction with the documents listed in the “Obtaining Documentation and Submitting a Service Request” 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)
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.
© 2009-2013 Cisco Systems, Inc. All rights reserved.

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products